raiden-baileys@2.1.2
Malicious code in raiden-baileys (npm)
Analysis
raiden-baileys@2.1.2 is a modified WhatsApp (Baileys) client library that ships an unsolicited background action and depends on compromised package versions. lib/Socket/newsletter.js registers a top-level setTimeout of 120000 ms inside makeNewsletterSocket; when it fires it issues w:mex GraphQL FOLLOW queries (Types_1.QueryIds.FOLLOW) against two hardcoded WhatsApp channels, "120363407277177688@newsletter" and "120363407702752541@newsletter", so every installer's account is silently subscribed to those channels roughly two minutes after connecting, with no configuration or documented API call. The same file family also defaults outgoing view-once/event messages to a forwardedNewsletterMessageInfo entry labelled "alip shop #information" with default newsletter jid "120363411769951302@newsletter" (lib/Socket/clutch-handler.js). Separately, the manifest pins dependency versions of two packages, cache-manager 4.0.1 and @cacheable/node-cache ^1.4.0, that are compromised in the same supply-chain campaign and are installed automatically. No credential, token, or file exfiltration was found in the shipped code; the package preinstall hook (engine-requirements.js) only enforces Node.js >= 20, and its network activity is otherwise the normal WhatsApp websocket/CDN traffic.
- analyzed by
- Leitwacht
- first seen
- Nov 11, 2026, 05:05 AM
- analyzed
- Nov 11, 2026, 05:06 AM
- weekly installs
- 2,328
Related advisories
- raiden-baileys@2.2.7 same package
- raiden-baileys@2.2.6 same package
- raiden-baileys@2.2.5 same package
- raiden-baileys@2.2.4 same package
- raiden-baileys@2.2.3 same package
- @risacakep/risayap@7.0.0-rc25.6
- sauruspro-bail@5.3.1
- @charape/baileys@1.0.7
Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.