Which versions of @crysnovax/baileys are malicious?

The following npm versions of @crysnovax/baileys are flagged malicious: 2.7.6, 2.7.10, 2.7.11, 2.7.12, 2.7.13, 2.7.14, 2.7.15, 2.7.16, 2.7.17, 2.7.18, 2.7.19, 2.7.20, 2.7.21, 2.8.0, 2.8.1, 2.8.2, 2.8.3. Treat any of these as compromised.

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

@crysnovax/baileys 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 @crysnovax/baileys — how do I know if it already compromised me?

If @crysnovax/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 @crysnovax/baileys part of a known attack campaign?

Yes — @crysnovax/baileys is associated with the GHSA-c34p-4828-cg5g 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 @crysnovax/baileys across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @crysnovax/baileys (17 malicious versions).

Malicious package

@crysnovax/baileysnpm

Advisory published Sep 3, 2026Updated Sep 7, 2026

@crysnovax/baileys is a confirmed malicious npm package (MAL-2026-15917) that steals credentials and exfiltrates sensitive data (malicious versions 2.7.6, 2.7.10, 2.7.11…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @crysnovax/baileys (npm)

MAL-2026-15917

Immediate action

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

npm uninstall @crysnovax/baileys

What this malware does

@crysnovax/baileys is a renamed fork of the Baileys WhatsApp Web library. On every successful connection (connection.update with connection === 'open', wired in lib/Socket/socket.js) it silently makes the user's own authenticated WhatsApp account follow two channels controlled by the publisher, 120363402922206865@newsletter and 120363423670814885@newsletter, through the xwa2_newsletter_join_v2 FOLLOW query, with no opt-out and a creds.additionalData.crysnovaxFollowed once-flag. From 2.7.10 the module that performs the follow (lib/Utils/channel-policy.js) is the only file in the package run through javascript-obfuscator (declared as a devDependency with an 'obfuscate' npm script); pkgwarden re-implemented the rotated string-table decoder to recover the channel ids without executing the code. Separately, from 2.7.6, lib/Utils/integrity.js POSTs the package name and version plus a SHA-256 machine fingerprint to https://bailey.crysnovax.link/api/v1/verify on every connect (a publisher-controlled kill switch that fails open), and the update check is repointed to web.crysnovax.link. Earlier versions (1.0.3 through 2.7.5) carry the same forced follow in plaintext with a comment calling it a 'condition of use'; they are not listed here. The listed versions combine the concealed follow with the fingerprint phone-home. Reachability was confirmed by following the socket chain from makeWASocket. No credential or session-key theft was observed. All listed versions were fetched from the npm registry and read by hand on 2026-09-03; the current latest tag (2.8.3) is armed. Related family: MAL-2026-13932 and MAL-2026-15819 (Baileys-fork newsletter auto-follow campaign).

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

17 flagged

2.7.62.7.102.7.112.7.122.7.132.7.142.7.152.7.162.7.172.7.182.7.192.7.202.7.212.8.02.8.12.8.22.8.3

Indicators of compromise (SHA-256)

2d2f02ca84b3529942643704a1fd8e05dd25f63a293ec05bf6c33cf004b1b31c

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @crysnovax/baileys (17 malicious versions).
If you installed it — respond
@crysnovax/baileys 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 @crysnovax/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. @crysnovax/baileys on npm has been identified as a malicious package (versions 2.7.6, 2.7.10, 2.7.11, 2.7.12, 2.7.13, 2.7.14, 2.7.15, 2.7.16, and 9 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-c34p-4828-cg5g

References

Credits

pkgwarden · finder

Detect & block this

O3 blocks @crysnovax/baileys-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