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

sauruslord-baileysnpm

sauruslord-baileys is a confirmed malicious npm package (MAL-2026-10661) that executes malicious code on install (malicious versions 3.0.0, 3.0.1, 3.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sauruslord-baileys (npm)

MAL-2026-10661
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall sauruslord-baileys

What this malware does

The package was found to contain malicious code or consuming dependency that contains malicious code

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

3 flagged
3.0.03.0.13.0.2

Indicators of compromise (SHA-256)

57bf5b42dfbe58c4ce2206575237a6823d3eb3281b3ec5aaae94133e831a0dd0
474b90ec19af5dbbc5bf3c8d27c0c4d079c7d980d6e3316dad3bbf5682abbe52
ed27885539634a9ead0ef6cbafcadcc2b0ac4218f5eb5192d2ae420df0588e16
f34d91a9ac6cc9876e76c0ef73964efdefd87ff83eb59ad798df6a6fa0b80d7e

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 sauruslord-baileys (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sauruslord-baileys across your stack and pipelines.

  2. If you installed it — respond

    Remove sauruslord-baileys 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 sauruslord-baileys 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 sauruslord-baileys 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. sauruslord-baileys on npm has been identified as a malicious package (versions 3.0.0, 3.0.1, 3.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-h2r9-2p5m-9f8gIN-MAL-2026-010642IN-MAL-2026-010641IN-MAL-2026-010640

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks sauruslord-baileys-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.

Explore

sauruslord-baileys (npm) malicious package — MAL-2026-10661 | O3 Security