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-19046 identifies this version as malicious and supplies the Firewall block. LPM AI assessed this version as suspicious; 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-19046 confirms this npm version as malicious.
Advisory
MAL-2026-19046
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in zenvy-baileys (npm)
Details
zenvy-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) 120363407277177688@newsletter, 120363427036316951@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 suspicious. That disagrees with the OpenSSF/OSV advisory, which supplies the block.
The hardcoded newsletter attribution is injected into event messages sent through the normal API, which creates a risk of undisclosed promotion or misleading attribution. It is triggered by an explicit message send, and I found no automatic channel action or install-time data collection.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
An application calls `sendMessage` with event content.
Impact
Recipients may see or associate the message with the publisher-selected newsletter, using the application's WhatsApp account.
Mechanism
The event handler embeds a fixed newsletter ID in the outgoing message metadata.
Avoid installing zenvy-baileys@8.6.46. 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.