@jexkcode/baileys@1.3.1
Malicious code in @jexkcode/baileys (npm)
Analysis
An unofficial third-party fork of the baileys WhatsApp Web API library, shipped under an unrelated package scope, that silently enrols the accounts it connects on into a fixed WhatsApp channel. lib/Utils/auto-follow.js hardcodes the newsletter JID 120363405612723183@newsletter in a constant labelled "HARDCODED for jexkcode" and exports setupAutoFollow(), which lib/Socket/index.js calls unconditionally from makeWASocket(). Consequently, about three seconds after every successful 'connection.update' -> open event, the library calls sock.newsletterFollow('120363405612723183@newsletter'), ignores the integrator's configuration, gives the application no opt-out, and swallows any error, leaving the follow invisible to the account owner. Every bot, notifier or automation built on this library is made to follow that channel, inflating the channel operator's follower count with accounts that never consented. The behaviour is not disclosed in the package documentation. It ships no credential-harvesting code: the only network destinations present in the tree are the standard WhatsApp endpoints (web[.]whatsapp[.]com, call[.]whatsapp[.]com) and an api[.]openai[.]com call in the optional voice-note transcription helper, and the only lifecycle hook (engine-requirements.js) merely enforces a minimum Node.js version.
- analyzed by
- Leitwacht
- first seen
- Nov 7, 2026, 01:04 PM
- analyzed
- Nov 7, 2026, 01:22 PM
- weekly installs
- 382
Related advisories
- @jexkcode/baileys@1.2.0 same package
- sauruspro-bail@5.0.2
- charape@1.0.20
- @yuanjielab/cli@0.10.1
- @memtensor/memos-cloud-openclaw-plugin@0.1.22
- raiden-baileys@2.2.1
- raiden-baileys@2.2.0
- neun-by-neun@0.1.0
Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.