@denzy-official/baileys@1.2.8
Malicious code in @denzy-official/baileys (npm)
Analysis
This package is an unofficial republish of the WhatsApp client library baileys under a different scope (@denzy-official) than the upstream project. It performs two actions the installer does not expect. First, lib/index.js executes base64-encoded source through eval(Buffer.from(...,'base64').toString()) as soon as the module is required; the decoded payload prints a "Baileys Custom By Denzy ZeroDay" ASCII banner and advertises the Telegram handle @pantatBegetar. Second, lib/Socket/newsletter.js schedules, at module load, a call delayed by 90 seconds (with a further 5-second repeat) that issues a newsletterWMexQuery FOLLOW request for a hardcoded, base64-encoded WhatsApp channel JID, 120363402308105961@newsletter — silently making the connected WhatsApp account follow the operator's channel. The package also fetches version metadata at runtime from an unofficial GitHub fork, hxxps://raw[.]githubusercontent[.]com/Denzy-Z3roDay/baileys/master/src/Defaults/baileys-version[.]json, rather than the upstream source. The preinstall hook (node ./engine-requirements.js) only checks the Node.js version. No credential, token or environment-variable harvesting was found in the package.
- analyzed by
- Leitwacht
- first seen
- Nov 15, 2026, 08:56 AM
- analyzed
- Nov 15, 2026, 08:58 AM
Related advisories
- @denzy-official/baileys@1.2.9 same package
- @denzy-official/baileys@1.2.7 same package
- alisaai-baileys@10.0.0
- raiden-baileys@2.2.6
- raiden-baileys@2.2.5
- @trashcore/baileys@4.1.5
- @zanxiky/baileys@1.1.0
- @skycodee/baileys@8.0.15
Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.