@zanta/baileys
This report shows the evidence for @zanta/baileys@1.0.1. 2 of 4 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
This package appears in our research on the malicious Baileys forks, with how it works, the full package list and what to do if you installed it.
OpenSSF/OSV Malicious Advisory
imported 21d ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-17443 confirms this npm version as malicious.
Advisory
MAL-2026-17443
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @zanta/baileys (npm)
Details
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/socket.js` line 23 declares the plain-literal `AUTO_FOLLOW_CHANNEL_JID = "120363406265537739@newsletter"`; lines 769-794, in the login-success (`CB:success`) handler, wait 3 seconds after the connection opens and send a FOLLOW query (`xwa2_newsletter_join_v2`) for it (cited line 774: `QueryIds.FOLLOW,`), suppressing "already subscribed" errors. There is no opt-out. The package README describes the fork as one from which "annoying developer auto-follow newsletter scripts have been completely stripped", which the shipped code contradicts.
Line numbers refer to version 1.0.1; 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: `c88f9688c56742da9b149da3c41df88da47fe95073ad581a716fc4c11ee199f3`; 1.0.1: `dc0eb5fcdfa84de88afe9eaf4bea9d6360fa984797599a1b7d7737df1d341c2a`.
References
Independent scan evidence
public snapshotBehavioral surface
ChildProcessCryptoFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
Oversized source lightweight scan
WAProto/index.js4.23 MB file, sampled 256 KB
Source & flagged code
7 flagged · loading sourcelib/WABinary/constants.jsView file
600patternName = google_api_key
severity = high
line = 600
High
High Secret
Package contains a high-severity secret pattern.
lib/WABinary/constants.jsView on unpkg · L600600patternName = google_api_key
severity = high
line = 600
High
Secret Pattern
Google API key in lib/WABinary/constants.js
lib/WABinary/constants.jsView on unpkg · L600lib/Utils/validate-connection.jsView file
114pull: false,
L115: devicePairingData: {
L116: buildHash: appVersionBuf,
...
L141: const { details, hmac, accountType } = proto.ADVSignedDeviceIdentityHMAC.decode(deviceIdentityNode.content);
L142: let hmacPrefix = Buffer.from([]);
L143: if (accountType !== undefined && accountType === proto.ADVEncryptionType.HOSTED) {
...
L165: ]);
L166: account.deviceSignature = Curve.sign(signedIdentityKey.private, deviceMsg);
L167: const identity = createSignalIdentity(lid, accountSignatureKey);
Findings
4 High4 Medium4 Low
HighHigh Secretlib/WABinary/constants.js
HighSemantic Analysis LimitedWAProto/index.js
HighKnown Malware Source Similaritylib/Utils/messages-media.js
HighSecret Patternlib/WABinary/constants.js
MediumNetwork
MediumShips Build HelperWAProto/GenerateStatics.sh
MediumOversized Source FileWAProto/index.js
MediumStructural Risk Force Deep Review
LowWeak Cryptolib/Utils/validate-connection.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @zanta/baileys@1.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing @zanta/baileys@1.0.1. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.