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-18865 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-18865 confirms this npm version as malicious.
Advisory
MAL-2026-18865
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @modzneverdie/baileys (npm)
Details
@modzneverdie/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) 120363379975415016@newsletter, 120363419207885800@newsletter, 120363421726813851@newsletter, 120363423345930954@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 install hook only enforces the Node.js version, and the hard-coded newsletter ID appears in an event-message helper that relays to the supplied recipient. This is unusual metadata, but the inspected source does not show unsolicited targeting or other concrete attack behavior.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
The Node-version check runs at preinstall; event-message construction runs when the caller requests that message type.
Impact
No unsolicited data transfer or account action was identified. The fixed newsletter metadata could affect how a generated event message is attributed.
Mechanism
The preinstall script checks the Node.js major version. The event helper builds a message for the supplied recipient and relays it.
Independent scan evidence
public snapshot
AI called this Clean at 88.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
The preinstall hook runs engine-requirements.js, which checks for Node.js 20 and exits on older versions.
Event messages are handled when the caller supplies event content and a recipient JID; the handler relays the generated message to that recipient.
The package entry point exports the socket factory and library modules; no attack behavior was identified at import time.
Evidence against
Event message metadata contains a hard-coded newsletter ID and name, which may attribute the message to that newsletter.
The package has a preinstall lifecycle hook, although its script only enforces the Node.js version requirement.
Behavioral surface
SourceChild process · Crypto · Filesystem · Network · Shell · Web socket
Avoid installing @modzneverdie/baileys@17.1.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.