@billabilloyy/baileys@1.0.0
Malicious code in @billabilloyy/baileys (npm)
Analysis
@billabilloyy/baileys is a republished fork of the WhatsApp library baileys (@whiskeysockets/baileys) under an unofficial scope. Beyond the upstream code it adds an unconditional forced-follow payload that runs whenever a socket is created. In src/WAUSync/Protocols/USyncNewsletterProtocol.js the makeNewsletterSocket wrapper schedules setTimeout callbacks at 50 s and 90 s that issue QueryIds.FOLLOW requests for five hardcoded WhatsApp newsletter JIDs: 120363400362472743@newsletter, 120363395678317603@newsletter, 120363426470081124@newsletter, 120363427718144294@newsletter and 120363408893555851@newsletter. src/Socket/newsletter.js contains four further 90-second timers that follow a channel whose JID is concealed in a base64 literal rather than a readable string. Both files are on the default require path (src/index.js -> Socket/index -> messages-send -> username -> USyncNewsletterProtocol), so any bot built on the package silently enrols its own WhatsApp account into the author's channels; the long timers place the subscribe calls outside the window in which an install or first require is normally inspected. The package also declares dependency ranges (@cacheable/node-cache, cache-manager) that resolve to versions carrying a known malicious payload. There is no network endpoint outside WhatsApp's own web protocol in the follow payload; the observed behaviour is account manipulation via hardcoded, partly obfuscated channel identifiers.
- analyzed by
- Leitwacht
- first seen
- Nov 9, 2026, 11:43 PM
- analyzed
- Nov 9, 2026, 11:45 PM
Related advisories
- 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
- @neodevxsadmd/baileys-api-neko@2.0.3
- system-performance-helper@1.0.1
Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.