Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@mr-supun-fernando/supunmd-bailnpm

@mr-supun-fernando/supunmd-bail is a confirmed malicious npm package (MAL-2026-16387) that executes malicious code on install (malicious version 3.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @mr-supun-fernando/supunmd-bail (npm)

MAL-2026-16387
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @mr-supun-fernando/supunmd-bail

What this malware does

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.

Malicious versions

1 flagged
3.0.3

Indicators of compromise (SHA-256)

86c68c82f6ead4ab3b823b81fd6805991bfdd65cdc901d83aeb561cdd8f27b19

Detection & response playbook

Malicious package

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @mr-supun-fernando/supunmd-bail (version 3.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @mr-supun-fernando/supunmd-bail across your stack and pipelines.

  2. If you installed it — respond

    Remove @mr-supun-fernando/supunmd-bail from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If @mr-supun-fernando/supunmd-bail was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks @mr-supun-fernando/supunmd-bail before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @mr-supun-fernando/supunmd-bail on npm has been identified as a malicious package (version 3.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020293

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @mr-supun-fernando/supunmd-bail-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
@mr-supun-fernando/supunmd-bail (npm) malicious package — MAL-2026-16387 | O3 Security