Advisory

MAL-2026-18683

Also known as: None

Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.

Summary

Malicious code in @zaxius/baileys (npm)

Details

@zaxius/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) , using the victim's authenticated session and without telling them. Same behaviour as the PhantomSub family (MAL-2026-17342).

---
_-= Per source details. Do not edit below this line.=-_

Source: amazon-inspector (b581af4dbb7da9107894388cf6b64ff1aa9762e9be48c818ea488a38b561ae0f)
This fork of the Baileys WhatsApp library ships two notable behaviors. (1) package.json declares the runtime dependency libsignal as github:tenka-san/libsignal-node with no commit SHA, tag, or integrity check. npm install resolves this against whatever the default branch of that repository currently points at, so whoever controls that GitHub account/branch controls code pulled into the installer's dependency tree on every install, outside of npm registry integrity. (2) When a consumer constructs a WhatsApp socket, a timer (~150s) fetches a JSON array of newsletter JIDs from raw.githubusercontent.com/MichaelWens/idnewsletter/refs/heads/main/newsletters.json — a mutable main branch — and iterates calling newsletterWMexQuery(jid, QueryIds.FOLLOW) on each, using the installer's authenticated WhatsApp account to follow those channels. This behavior is not documented in the README and the list is author-mutable at any time.

Severity

Not rated by the source.

Dates

Published
2026-10-26 00:00 UTC
Modified
2026-11-13 03:45 UTC

Affected packages and fixes

@zaxius/baileys

npm · All systems

Affected

  • Versions: 1.0.1

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: OpenSSF Malicious Packages · Apache-2.0

Sources & licences