Which versions of danz-bails are malicious?

The following npm versions of danz-bails are flagged malicious: 1.0.0, 1.1.0. Treat any of these as compromised.

How do I remediate danz-bails if I installed it?

danz-bails is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed danz-bails — how do I know if it already compromised me?

If danz-bails 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 danz-bails across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for danz-bails (2 malicious versions).

Malicious package

danz-bailsnpm

Advisory published Oct 1, 2026Updated Oct 2, 2026

danz-bails is a confirmed malicious npm package (MAL-2026-17444) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in danz-bails (npm)

MAL-2026-17444

Immediate action

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

npm uninstall danz-bails

What this malware does

This package is a fork of the Baileys WhatsApp Web library (npm) and belongs to the "PhantomSub" family described by OX Security in September 2026: the publisher injected code that, without the installer asking, uses the installer's own authenticated WhatsApp session to subscribe that account to WhatsApp Channels (newsletters) the publisher chose, by sending the WhatsApp w:mex FOLLOW query (query_id 7871414976211147) for each target channel JID.

package/lib/Socket/newsletter.js lines 62-90 (cited line 68: QueryIds.FOLLOW) run in the body of makeNewsletterSocket, so they fire whenever a socket is created: 10 seconds later, and then at 3-second intervals, the code sends FOLLOW queries for three channel JIDs, each stored as a base64 literal decoded with Buffer.from(..., "base64"): 120363424403369453@newsletter, 120363423038562425@newsletter and 120363427530519865@newsletter. There is no option to turn this off and the README does not mention it.

Separately, package/lib/Socket/danz-auto-follow.js follows the channel behind invite code 0029VbD7H6m9MF9ALdskro07 on connect. That one is documented in the 1.1.0 README with a danzAutoFollowChannel: false opt-out; the base64-hidden follow of the three JIDs above is not.

Line numbers refer to version 1.1.0; the same code is present in every published version listed under affected.

Static review of the published tarball(s) found no code that sends WhatsApp credentials or session keys off-host, no install-time payload (the only install hook is Baileys' stock Node.js version check in engine-requirements.js), and no persistence; the payload runs when an application creates a WhatsApp socket with the library. The harm is the covert use of the victim's account to inflate the publisher's channel subscribers.

SHA-256 of the published npm tarball(s): 1.0.0: 1b568e46aa2ffbb186319e72b9fed52dde060f99319a82003d9d2ac15410dbbd; 1.1.0: 7370d73e2e5a0434fe41fc033ba9fc91d624a8a9461188fda82e04e3873e6d26.

Malicious versions

2 flagged

1.0.01.1.0

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for danz-bails (2 malicious versions).
If you installed it — respond
danz-bails is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If danz-bails 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. danz-bails on npm has been identified as a malicious package (versions 1.0.0, 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

Rising Sun Solutions LLC · finder

Detect & block this

O3 blocks danz-bails-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database