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-18859 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-18859 confirms this npm version as malicious.
Advisory
MAL-2026-18859
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @kyuu2nd/baileys (npm)
Details
@kyuu2nd/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) 120363330344810280@newsletter, 120363400738305381@newsletter, 120363402868866359@newsletter, 120363404790454890@newsletter, 120363404861802607@newsletter, 120363405313529091@newsletter and 13 more (stored as character-code arrays) and a list downloaded at runtime from https://raw.githubusercontent.com/kiuur/IDCH/refs/heads/main/idch.json, 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 lifecycle hook only enforces the Node version requirement. The import-time GitHub fetch carries no user data, and the flagged newsletter reference is part of caller-triggered event messaging rather than an automatic action toward that newsletter.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
The version check runs during preinstall; the update request runs when the package entrypoint is imported. Newsletter actions require an explicit method call.
Impact
No credential collection, data exfiltration, install-time network contact, or automatic account action was identified.
Mechanism
The preinstall script checks process.versions.node. The entrypoint fetches and prints update text. The flagged newsletter ID appears in generated event metadata, while the message is relayed to the caller-provided JID.
AI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
The preinstall script only runs a Node.js version check and exits when Node is older than 20.
The import entrypoint fetches update information from a raw GitHub URL and prints the returned message; the request includes no package, host, or user data.
The flagged newsletter ID is message metadata in an event helper that builds a message for the caller-supplied JID.
Newsletter follow and unfollow actions are explicit methods that take a JID argument.
Evidence against
The package makes a hard-coded network request on import to retrieve and display an update notice.
The source contains a hard-coded newsletter ID, but it is used in event-message metadata rather than as the message destination.
Behavioral surface
SourceChild process · Crypto · Filesystem · Network · Shell · Web socket
Avoid installing @kyuu2nd/baileys@2.0.6. 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.