Which versions of sauruspro-bail are malicious?

The following npm versions of sauruspro-bail are flagged malicious: 0.0.0-stage, 5.0.0, 5.0.1, 5.0.2-alpha.spr.test. Treat any of these as compromised.

How do I remediate sauruspro-bail if I installed it?

Remove sauruspro-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.

I already installed sauruspro-bail — how do I know if it already compromised me?

If sauruspro-bail was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find sauruspro-bail across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for sauruspro-bail (4 malicious versions).

Malicious package

sauruspro-bailnpm

Advisory published Nov 3, 2026Updated Nov 10, 2026

sauruspro-bail is a confirmed malicious npm package (MAL-2026-19073) that executes malicious code on install (malicious versions 0.0.0-stage, 5.0.0, 5.0.1…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sauruspro-bail (npm)

MAL-2026-19073

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall sauruspro-bail

What this malware does

Malicious package. sauruspro-bail is a trojanized fork of the Baileys WhatsApp library (@whiskeysockets/baileys). it silently subscribes every victim (via the injected WhatsApp newsletter/channel FOLLOW on connect) to attacker-controlled WhatsApp channels — hardcoded newsletter JIDs: 120363418964199743@newsletter, 120363429190136593@newsletter. Legitimate Baileys never hardcodes a channel JID or auto-follows on connect; all published versions are malicious.

Malicious versions

4 flagged

0.0.0-stage5.0.05.0.15.0.2-alpha.spr.test

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for sauruspro-bail (4 malicious versions).
If you installed it — respond
Remove sauruspro-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.
Did it already run?
If sauruspro-bail was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. sauruspro-bail on npm has been identified as a malicious package (versions 0.0.0-stage, 5.0.0, 5.0.1, 5.0.2-alpha.spr.test flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

wormsign.io

Credits

wormsign · finder

Detect & block this

O3 blocks sauruspro-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