Which versions of @vanzxy/baileys are malicious?

Every published version of @vanzxy/baileys on npm is considered malicious. Remove the package entirely.

How do I remediate @vanzxy/baileys if I installed it?

Remove @vanzxy/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.

I already installed @vanzxy/baileys — how do I know if it already compromised me?

If @vanzxy/baileys 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.

Is @vanzxy/baileys part of a known attack campaign?

Yes — @vanzxy/baileys is associated with the GHSA-p29j-8jqp-jx9c campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @vanzxy/baileys across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @vanzxy/baileys (all published versions).

Malicious package

@vanzxy/baileysnpm

Advisory published Nov 3, 2026Updated Nov 5, 2026

@vanzxy/baileys is a confirmed malicious npm package (MAL-2026-18529) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @vanzxy/baileys (npm)

MAL-2026-18529

Immediate action

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

npm uninstall @vanzxy/baileys

What this malware does

@vanzxy/baileys is a fork of the Baileys WhatsApp Web library that silently subscribes the installer's own authenticated WhatsApp account to an author-chosen WhatsApp Channel. Part of the campaign OX Security documented as "PhantomSub" (2026-09-28): https://www.ox.security/blog/phantomsub-malicious-npm-campaign-secretly-adds-users-to-whatsapp-spam-channels/ . Static read of the published 2.0.4 tarball on 2026-10-16 (not executed) found a hardcoded channel JID 120363400911374213@newsletter together with the newsletter FOLLOW query wired to run automatically after the socket connects, with errors suppressed. Same family as the withdrawn MAL-2026-4519 (chromestaff-baileys 1.1.3). Live on npm with no OSV record as of 2026-10-16.

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

8aaf0ab3d240dca86b7e0bb0385dfb39a4aad4f3a0a44e21fb77b5b14e580862

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @vanzxy/baileys (all published versions).
If you installed it — respond
Remove @vanzxy/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.
Did it already run?
If @vanzxy/baileys 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. @vanzxy/baileys on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-p29j-8jqp-jx9c

References

Credits

OX Security · finder
Patrick Duggan, DugganUSA · reporter

Detect & block this

O3 blocks @vanzxy/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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database