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-18931 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-18931 confirms this npm version as malicious.
Advisory
MAL-2026-18931
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in alisaai-baileys (npm)
Details
alisaai-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 the channel ID(s) 120363401150921495@newsletter, 120363403865450077@newsletter, 120363421346448687@newsletter (stored as base64 strings), 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 preinstall hook only checks the Node.js version, and the publisher’s newsletter JID is embedded as attribution metadata in an event-message helper that relays to a caller-supplied recipient. The flagged subprocess supports ordinary video thumbnail generation, and no malicious behavior was identified in the inspected paths.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
Installation runs a Node.js version check; importing the main entry prints a banner; media and event helpers run when called by the application.
Impact
No automatic credential collection, unrelated network contact, or unsolicited account action was identified in the inspected paths.
Mechanism
The inspected code checks the runtime version, builds messages with publisher newsletter attribution metadata, relays messages to a supplied recipient, and invokes ffmpeg for thumbnail extraction.
Independent scan evidence
public snapshot
AI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
The preinstall script runs a Node.js version check that exits on versions below 20; it does not contact the network or inspect user data.
The hard-coded newsletter JID appears in event-message context metadata, and the code relays the constructed message to the caller-supplied JID when that event handler is used.
The media subprocess runs ffmpeg to extract a video thumbnail from the supplied media path.
Importing the main entry prints a publisher-branded banner and exports the library.
Evidence against
The manifest includes preinstall and prepare lifecycle scripts, but preinstall only runs the Node.js version check and prepare only prints a message.
The publisher newsletter identifier is embedded as message metadata; the inspected code does not automatically follow, join, or post to that channel.
The flagged child-process call is used for media thumbnail extraction, consistent with the package’s WhatsApp media features.
Behavioral surface
SourceChild process · Crypto · Filesystem · Network · Shell · Web socket
Avoid installing alisaai-baileys@11.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.