@raffnotdev/baileys@1.0.0
Malicious code in @raffnotdev/baileys (npm)
Analysis
This package republishes the @whiskeysockets/baileys WhatsApp Web library under the unofficial scope @raffnotdev/baileys with added behaviour the installer does not expect. lib/Socket/newsletter.js contains four hardcoded base64-encoded WhatsApp channel identifiers — 120363426470081124@newsletter, 120363419110835885@newsletter, 120363429563611349@newsletter and 120363424295522327@newsletter — which makeNewsletterSocket() decodes and follows via a newsletter-follow query on timers at 10, 15, 20 and 25 seconds. Because that factory is chained unconditionally into every consumer (makeNewsletterSocket → makeUsernameSocket → makeMessagesSocket), every account using the library is silently subscribed to those channels on first connect, while the README claims only one follow of the developer's own channel. lib/Socket/socket.js additionally injects a checkBan() helper that sends a phone number to a non-WhatsApp third-party endpoint, hxxps://kyuux-r[.]indevs[.]in/api/check-whatsapp?phone=..., with a browser User-Agent, and stamps an unrelated author handle ("t[.]me/luyatiem") onto the JSON response rather than the package's own. The preinstall hook (engine-requirements.js) only enforces Node.js >= 20; no token or credential exfiltration was found in the shipped code.
- analyzed by
- Leitwacht
- first seen
- Nov 5, 2026, 05:25 AM
- analyzed
- Nov 5, 2026, 05:28 AM
Related advisories
- gugodapis@1.0.0
- @adminide-stack/utils@0.0.16-130
- tailwindcss-hook-forms@0.5.2
- react-contact-forms@0.5.2
- tailwind-form-core@0.5.5
- tailwind-input-kit@0.5.5
- tailwind-forms-kit@0.5.5
- tailwind-contact-forms@0.5.8
Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.