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-18830 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-18830 confirms this npm version as malicious.
Advisory
MAL-2026-18830
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @fadelsm/baileys (npm)
Details
@fadelsm/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) 120363400362472743@newsletter, 120363406524087186@newsletter, 120363407144637058@newsletter, 120363408367338249@newsletter, 120363409508273158@newsletter, 12036340982021544@newsletter and 4 more (stored as character-code arrays), 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 package silently adds a publisher-chosen newsletter attribution to outgoing EVENT messages, creating a real but limited promotion risk. The evidence does not show an automatic account action such as following the newsletter or posting to it, so this warrants a warning rather than a block.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
The application sends a WhatsApp EVENT message through the package's send-message handler.
Impact
Recipients may see or access the publisher's newsletter through metadata added without an explicit request. No automatic follow or post to the newsletter was identified.
Mechanism
The event handler adds a publisher-chosen newsletter JID to forwarded-newsletter metadata, then relays the message to the requested recipient.
Evidence
lib/Socket/dugong.jslib/Socket/messages-send.js
Independent scan evidence
public snapshot
AI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for AI warning decision
Sending an EVENT message adds a fixed newsletter ID, `120363420091867664@newsletter`, to its forwarded-newsletter metadata.
The event handler relays the constructed message to the requested recipient.
The preinstall script only checks the Node.js major version and exits if it is below 20.
Evidence against
The newsletter attribution is added only in the EVENT message handler, not on package import or socket startup.
The newsletter API exposes follow and unfollow as explicit calls; no automatic follow to the fixed newsletter was identified.
The manifest's prepare script is empty, and the preinstall script contains only the Node.js version check.
Behavioral surface
SourceChild process · Crypto · Filesystem · Network · Shell · Web socket
Avoid installing @fadelsm/baileys@7.0.9. 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.