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.
Blocked by malware advisory
OpenSSF/OSV malware advisory MAL-2026-18904 identifies this version as malicious and supplies the Firewall block. LPM AI assessed this version as clean; the assessments disagree.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
OpenSSF/OSV malicious advisory
published · by OpenSSF/OSV
OpenSSF/OSV advisory MAL-2026-18904 confirms this npm version as malicious.
Advisory
MAL-2026-18904
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @thunderx/baileys (npm)
Details
@thunderx/baileys is a fork of the Baileys WhatsApp Web library that silently subscribes the installer's own WhatsApp account to WhatsApp Channels chosen by the publisher. When the socket connects, code in lib/Socket/newsletter.js sends the WhatsApp w:mex FOLLOW query for a list downloaded at runtime from https://raw.githubusercontent.com/yun-xiaogt/ivory-lotus/refs/heads/main/newsletter.json, using the victim's authenticated session and without telling them. Same behaviour as the PhantomSub family (MAL-2026-17342).
LPM's AI review found this version clean. That disagrees with the OpenSSF/OSV advisory, which supplies the block.
The lifecycle hook only enforces the declared Node.js requirement, and the flagged newsletter identifier is included as metadata on event messages sent to a caller-selected recipient. The main entry does make an unsolicited request for an update notice at import time, but the inspected code does not transmit user or package data.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
Package installation runs the Node version check; importing the main entry fetches and displays an update notice; event metadata is sent only when the caller sends an event message.
Impact
No credential collection, unrelated account action, or data exfiltration was identified. Importing the entry point does make an unsolicited request to retrieve the update notice.
Mechanism
The update request retrieves JSON from raw.githubusercontent.com. Event messages are relayed to the recipient jid supplied to sendMessage; the hard-coded newsletter identifier is embedded in message context metadata.
AI called this Clean at 86.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
The preinstall hook only runs a Node.js version check; prepare is empty.
The version check exits on Node versions below 20 and does not access files or the network.
The hard-coded newsletter ID appears in event-message metadata, while the message recipient comes from the caller-provided jid.
Event messages are relayed to that caller-provided jid when sendMessage handles an explicit event message.
The import-time request fetches an update notice from raw.githubusercontent.com and prints its text; it does not send package or user data.
Evidence against
Importing lib/index.js makes an unsolicited request to raw.githubusercontent.com to display an update notice. This is unrelated to the core WhatsApp client behavior.
Behavioral surface
SourceChild process · Crypto · Filesystem · Network · Shell · Web socket
Avoid installing @thunderx/baileys@2.0.0. 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.