@violetix/baileys@0.6.0
Malicious code in @violetix/baileys (npm)
Analysis
This package reuses the upstream `baileys` package basename under an unrelated npm scope, presenting itself as a drop-in fork of the well-known WhiskeySockets/Baileys WhatsApp client, while shipping an unsolicited account-enrolment routine. In lib/Socket/newsletter.js the package registers an unconditional connection.update handler: whenever the WhatsApp connection opens it issues a newsletter-join query (QueryIds.FOLLOW against XWAPaths.xwa2_newsletter_join_v2) for the hardcoded channel 120363417337256584@newsletter, silently subscribing the account running the library to that channel. There is no configuration option to disable it, and the accompanying log line names a different channel (120363203083379699@newsletter), so the subscription is not reported to the operator. The bundled README states the fork does not auto-follow newsletter channels, which the shipped code contradicts. The package's only lifecycle hook, engine-requirements.js, merely checks that process.versions.node is 20 or newer. Outbound network destinations in the code are WhatsApp endpoints (wss://web[.]whatsapp[.]com/ws/chat, graph[.]whatsapp[.]com, acs[.]whatsapp[.]com); no credential, token or file-read exfiltration was found.
- analyzed by
- Leitwacht
- first seen
- Nov 12, 2026, 02:48 PM
- analyzed
- Nov 12, 2026, 03:06 PM
- weekly installs
- 1,017
Related advisories
- @violetix/baileys@0.5.7 same package
- @violetix/baileys@0.6.1 same package
- @violetix/baileys@0.5.5 same package
- @violetix/baileys@0.5.1 same package
- wertybailz@1.0.10
- @arkanhahaha/baileys@1.0.0
- @denzz221/baileys@8.1.3
- @denzz221/baileys@7.0.0
Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.