baileys-cleannpm
Advisory published Updated
baileys-clean is a confirmed malicious npm package (MAL-2026-19947) that executes malicious code on install (malicious version 7.3.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in baileys-clean (npm)
What this malware does
baileys-clean 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. makeNewsletterSocket in lib/Socket/newsletter.js contains a self-invoking property named newsletterAutoFollowSilent that registers a connection.update listener at socket creation; 15 seconds after every 'open' it calls newsletterWMexQuery(id, QueryIds.FOLLOW) for each of four hardcoded channel IDs (120363406225530257@newsletter, 120363408101167880@newsletter, 120363419318051000@newsletter, 120363421412174731@newsletter), 3.5 seconds apart, swallowing errors, and then repeats the whole loop every 60 seconds for as long as the socket is open. The README states the fork has no hidden auto-follow and documents an explicit opt-in function, autoFollowOwnerChannels, that does not exist anywhere in the shipped code; the only follow path is the automatic one. Same behaviour as the PhantomSub family (MAL-2026-17342).
Malicious versions
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for baileys-clean (version 7.3.2).
If you installed it — respond
Remove baileys-clean from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If baileys-clean was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
References
Credits
- CyberXYZ · finder
Detect & block this
O3 blocks baileys-clean-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.