npm · Malicious package advisory
Malware@mr-supun-fernando/supunmd-bail
GHSA-4w3g-g5h8-rw39
Malicious code in @mr-supun-fernando/supunmd-bail (npm)
Details
**Severity:** Critical **Affected versions:** `= 3.0.3` ## Source: amazon-inspector (86c68c82f6ead4ab3b823b81fd6805991bfdd65cdc901d83aeb561cdd8f27b19) package.json declares `"libsignal": "github:tenka-san/libsignal-node"` — an off-registry dependency source pointing at a personal-user GitHub repository with no commit SHA, no tag, and no integrity check. On `npm install`, npm clones the current tip of that repository and installs whatever it contains, running any lifecycle scripts (`preinstall`/`install`/`postinstall`/`prepare`) inside the fetched tree on the installer's machine. The dependency key `libsignal` shadows the well-known Signal protocol library, but the source is a personal user's fork rather than the upstream signalapp organization, so whoever controls the tenka-san/libsignal-node repository controls install-time code execution on every installer of this package. The source is mutable — content that resolves benign today can be replaced without any change to this package. A secondary observation: lib/Utils/generics.js line 403 references `ping`, but this is unrelated to the primary install-time execution concern. --- Credit: [OpenSSF](https://github.com/ossf/malicious-packages) ([source](https://github.com/ossf/malicious-packages/blob/403af799bbca20d1c7bc2682a4736256aaf2941c/osv/malicious/npm/@mr-supun-fernando/supunmd-bail/MAL-2026-16387.json)) **References:** - https://github.com/ossf/malicious-packages/blob/403af799bbca20d1c7bc2682a4736256aaf2941c/osv/malicious/npm/@mr-supun-fernando/supunmd-bail/MAL-2026-16387.json - https://www.npmjs.com/package/@mr-supun-fernando/supunmd-bail/v/3.0.3 - https://github.com/advisories/GHSA-4w3g-g5h8-rw39
Compromised versions (1)
- = 3.0.3
Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.