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 47-65 (cited line 58: QueryIds.FOLLOW) define an array of three base64 strings and, 90 seconds after the newsletter socket is created, decode each with Buffer.from(channel, "base64") and send a FOLLOW query, 6 seconds apart. Decoded JIDs: 120363387182851100@newsletter, 120363371199176376@newsletter and 120363421367985094@newsletter. There is no opt-out and the behavior is not documented.
Line numbers refer to version 1.0.0.
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: 9bc787ecc07e18d2504ab4e06e97d86d13a9952515a529a28b53a227d247b294.
{
"iocs": {
"files": [
{
"digests": {
"sha256": "47a91a2dc5cf922b819aad1da113a1d7999f402cd919c494f2cf30777d074ea7"
},
"note": "File containing the injected WhatsApp Channel follow code.",
"paths": [
"package/lib/Socket/newsletter.js"
],
"source": "PACKAGE_ARCHIVE"
}
]
}
}