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 Node.js version requirement, and importing the package exports the WhatsApp socket factory without creating a connection. The flagged secret-like string is a protocol token value, while the process execution supports video thumbnail extraction.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
Installation runs a Node.js version check; runtime network and media operations occur when callers use the library’s WhatsApp features.
Impact
No automatic credential collection, unrelated data transmission, or unrequested account action was identified.
Mechanism
The preinstall hook checks the Node.js major version. The inspected entry point exports modules without creating a socket, and the flagged process call is for ffmpeg video thumbnail extraction.
Network endpoints2
web.whatsapp.comraw.githubusercontent.com
Independent scan evidence
public snapshot
AI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
The preinstall hook only runs engine-requirements.js, which checks the Node.js major version and exits on versions below 20.
The package entry point exports the WhatsApp socket factory and library modules; it does not create a socket at import time.
The API-key-like string appears among protocol token dictionary values in lib/WABinary/constants.js.
The media helper runs ffmpeg to extract a video thumbnail, a function tied to media processing.
Evidence against
The package handles WhatsApp connections and media, so its WhatsApp network access and media processing are consistent with its stated purpose.
The scanner’s secret and process-execution signals have benign source context: a protocol token value and an ffmpeg thumbnail helper.
Behavioral surface
SourceChild process · Crypto · Filesystem · Network · Shell · Web socket
Supply chainHigh entropy strings · URL strings
ManifestNo manifest risk signals triggered.
Scanned 100 files · 1.73 MB of source
5 external domains referenced
call.whatsapp.com
raw.githubusercontent.com
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
7 high · 4 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.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.