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-19055 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-19055 confirms this npm version as malicious.
Advisory
MAL-2026-19055
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @vanzky/baileys (npm)
Details
Malicious package. `@vanzky/baileys` is a trojanized fork of the Baileys WhatsApp library (@whiskeysockets/baileys). it silently subscribes every victim (via the injected WhatsApp newsletter/channel FOLLOW on connect) to attacker-controlled WhatsApp channels — hardcoded newsletter JIDs: 120363412479307951@newsletter, 120363413713776550@newsletter, 120363429868081610@newsletter. Legitimate Baileys never hardcodes a channel JID or auto-follows on connect; all published versions are malicious. Detected by wormsign static analysis of the injected channel-subscription code.
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 documented Node version requirement, and the package entrypoint does not invoke the dormant follow helper. That helper would perform a publisher-selected account action if called, but the reviewed source does not show a default path that calls it.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Installation runs a Node version check; import shows a banner and exposes the library API.
Impact
No default account action or data collection was identified; the dormant helper could follow a newsletter and send a promotional message if explicitly called.
Mechanism
The inspected lifecycle hook checks the Node major version. The newsletter-follow helper is not exported by the Utils barrel or invoked by the package entrypoint.
Independent scan evidence
public snapshot
AI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
The preinstall hook runs a Node version check; it does not collect data or contact a host.
The package entrypoint creates and exports the WhatsApp socket, while the Utils barrel does not export the follow helper.
The unreferenced follow helper requires a caller to pass a socket before it registers an action on connection open.
The inspected protobufjs postinstall script checks dependency version compatibility and may print a warning.
Evidence against
The dormant follow helper contains code to follow a fixed newsletter invite and send a promotional message if called.
Behavioral surface
SourceChild process · Crypto · Environment variables · Filesystem · Network · Shell · Web socket
Supply chainHigh entropy strings · URL strings
ManifestNo manifest risk signals triggered.
Scanned 103 files · 1.73 MB of source
6 external domains referenced
call.whatsapp.com
raw.githubusercontent.com
t.me
wa.me
web.whatsapp.com
www.whatsapp.com
Oversized source lightweight scan
WAProto/index.js4.23 MB file, sampled 256 KB
No sampled risky behavior triggered.
Findings
6 high · 5 medium · 6 low
Where they are, most severe file first. Code opens a file's flagged lines, with their evidence, below.
Avoid installing @vanzky/baileys@1.0.2. 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.