@zanxiky/baileys@1.1.0
Malicious code in @zanxiky/baileys (npm)
Analysis
This package is a fork of the Baileys WhatsApp Web library with a hidden, self-invoking action that subscribes the user's own authenticated WhatsApp account to a channel the user never chose. In lib/Socket/newsletter.js the module defines `newsletterIds = ["0029Vb9EQN59RZAWWZpeek3X="]` (a base64-encoded WhatsApp channel/newsletter JID, annotated "Vip / About Iky") and then, at module load time, schedules `setTimeout(..., 150000)` — a 2.5 minute delay — that decodes the JID and sends a `w:mex` newsletter query with query id 7871414976211147 (the FOLLOW mutation) over the caller's already-authenticated socket, waiting 5 seconds between entries and writing only an informational "Newsletter follow request sent" log after the follow has happened. Nothing in package.json, the exported API, or the calling code offers an opt-in or config toggle for this behaviour; merely importing the library from an authenticated session is enough to trigger it after the delay, and the delay is placed so the follow occurs long after package install/load inspection has finished. Upstream Baileys exposes newsletter following only as an explicit user-invoked `newsletterFollow(jid)` call and contains no hardcoded channel list or self-starting timer, so this block is an injected addition in the copied fork. The package also declares the dependency `cache-manager@^7.2.8` in its manifest. No credential, token, or .npmrc access was found in the shipped code; the preinstall hook (engine-requirements.js) only checks that Node.js is version 20 or newer.
- analyzed by
- Leitwacht
- first seen
- Nov 10, 2026, 05:35 AM
- analyzed
- Nov 10, 2026, 05:36 AM
Related advisories
- @skycodee/baileys@8.0.15
- @billabilloyy/baileys@1.0.0
- raiden-baileys@2.2.1
- @denzz221/baileys@8.0.8
- @denzz221/baileys@8.1.7
- mock-datas-lib@1.0.1
- tavern-ai-sdk@1.0.0
- scanstudy-pointer-bat@1.0.0
Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.