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 enforces the declared Node.js requirement, and the flagged newsletter ID is attached as metadata when the caller requests event-message handling. The inspected entry point and media helper show ordinary package behavior, with no malicious data flow identified.
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; event-message handling and thumbnail extraction run when their respective library functions are called.
Impact
No automatic credential collection, unrelated network contact, or unsolicited account action was found in the inspected paths.
Mechanism
The install hook checks the Node.js major version, while media processing invokes ffmpeg with the requested video and output paths. The newsletter ID is message metadata for a caller-supplied recipient.
Independent scan evidence
public snapshot
AI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
The preinstall hook runs engine-requirements.js, which only checks the Node.js major version and exits if it is below 20.
The prepare script only prints a package name; the main entry point’s import-time behavior is limited to clearing the console and printing a banner.
The hard-coded newsletter ID appears as forwarded-message metadata in handleEvent, which builds a message for the caller-supplied JID.
The ffmpeg subprocess is used by the media utility to extract a video thumbnail to the supplied destination path.
Evidence against
The main entry point has console side effects on import.
Event messages include the publisher’s newsletter ID as metadata.
Behavioral surface
SourceChild process · Crypto · Filesystem · Network · Shell · Web socket
Avoid installing alisaai-baileys@10.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.