LWA-2026-13530 confirmed malware

@dcloude/baileys@0.1.1

Malicious code in @dcloude/baileys (npm)

T1195.002 · Compromise Software Supply Chain

Analysis

This package is a modified fork of the well-known @whiskeysockets/baileys WhatsApp client that keeps the upstream library name as its basename under a different scope, and it is confirmed malware: a prior version under this name was already confirmed malicious. The payload is account-level abuse baked into the default configuration. lib/Defaults/index.js exports DEFAULT_AUTO_FOLLOW_CHANNELS, a hardcoded array of 22 or more WhatsApp newsletter (channel) JIDs, and lib/Socket/newsletter.js subscribes the operator's own WhatsApp account to every one of them the first time the socket reaches the 'open' connection state, by issuing newsletterWMexQuery(jid, QueryIds.FOLLOW) for each JID. It is presented as an opt-out default (`autoFollowChannels`), and a second allowlist guard (`blockAutoFollowChannels`) exists only to constrain which newsletters any later follow call may reach, so the package's default path is the forced subscriptions the user never asked for. The rest of the package is the genuine library: lib/Socket/graphql.js posts to wamo[.]whatsapp[.]net and the WhatsApp GraphQL endpoints, and lib/Utils/messages-media.js fetches media URLs supplied by callers. The package.json declares a preinstall hook, node ./engine-requirements.js, which only checks that the Node.js major version is 20 or higher and exits otherwise. Indicators: forced follows of newsletter JIDs 120363429884981859@newsletter, 120363411629646029@newsletter, 120363406620310731@newsletter, 120363429449887888@newsletter, 120363429324002976@newsletter, 120363413199437385@newsletter (and further 1203634*@newsletter JIDs in the same array).

analyzed by
Leitwacht
first seen
Nov 1, 2026, 02:08 AM
analyzed
Nov 1, 2026, 05:51 AM
weekly installs
542

Related advisories

browse all confirmed advisories →

Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.