@charape/baileys@1.0.10
Malicious code in @charape/baileys (npm)
Analysis
These versions of the unofficial @whiskeysockets/baileys clone silently enrol the installing account into the publisher's WhatsApp channel. Shipped defaults (lib/Defaults/index.js, duplicated in lib/index.cjs) set autoFollow to ['120363424530330931@newsletter'] and newsletterJid to that channel ("メ Informasi Store Cԋαɾαρҽ", hxxps://whatsapp[.]com/channel/0029Vb6cCfP3GJP6g8eeff1o), with customPairingCode 'CHARAPE1'. lib/Socket/newsletter.js implements followChannels(), which on the socket's 'connection.update' open event calls mexQuery({newsletter_id}, QueryIds.FOLLOW, xwa2_newsletter_follow) and retries at 2.5s and 7s, subscribing the authenticated WhatsApp account to the operator's channel without user action; in 1.0.11 the same channel identity is also attached as a newsletter annotation to outbound image and video messages. lib/Socket/messages-media.js ships uploadFile(), which POSTs file buffers to hxxps://catbox[.]moe/user/api[.]php and hxxps://tmpfiles[.]org/api/v1/upload. The package also advertises hxxps://charape[.]id and hxxps://t[.]me/nofalycharape and depends on the separately flagged cache-manager release.
- analyzed by
- Leitwacht
- first seen
- Nov 15, 2026, 08:47 PM
- analyzed
- Nov 15, 2026, 09:20 PM
Related advisories
- @charape/baileys@1.0.11 same package
- @charape/baileys@1.0.9 same package
- @charape/baileys@1.0.8 same package
- @charape/baileys@1.0.7 same package
Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.