@charape/baileys@1.0.8
Malicious code in @charape/baileys (npm)
Analysis
@charape/baileys is an unofficial branded clone of the WhatsApp Web library @whiskeysockets/baileys that silently enrols every user's WhatsApp account into the author's promotional channel. lib/Defaults/index.js ships the channel as a default connection setting (autoFollow: ['120363424530330931@newsletter'], newsletterJid, newsletterName 'メ Informasi Store Cԋαɾαρҽ', channelUrl hxxps://whatsapp[.]com/channel/0029Vb6cCfP3GJP6g8eeff1o), so any bot built on the library inherits it. lib/Socket/newsletter.js registers a 'connection.update' handler that, as soon as the WhatsApp connection opens for a paired session, sends a newsletter FOLLOW query (Types.QueryIds.FOLLOW / xwa2_newsletter_follow) for that JID over the WhatsApp websocket, retrying up to three times at 2.5s and 7s, with errors silently swallowed — there is no opt-in and no visible prompt to the account owner. The same JID and channel name are hardcoded as fallback defaults in lib/Utils/messages.js and lib/Socket/messages-send.js (injectNewsletterWatermark), so outgoing image and video messages can be annotated with the author's channel. The package additionally pins the non-canonical native addon 'whatsapp-rust-bridge' to an exact version (0.5.4) and depends on 'cache-manager' ^7.2.8 resolving to 7.2.10. No install-time lifecycle hook is present and the shipped code contains no credential, token or .npmrc harvesting and no C2 endpoint outside the WhatsApp servers and the self-promotional links charape.id and t[.]me/nofalycharape.
- analyzed by
- Leitwacht
- first seen
- Nov 12, 2026, 08:05 PM
- analyzed
- Nov 12, 2026, 08:06 PM
Related advisories
- @charape/baileys@1.0.11 same package
- @charape/baileys@1.0.10 same package
- @charape/baileys@1.0.9 same package
- @charape/baileys@1.0.7 same package
- raiden-baileys@2.2.3
- @thunderx/baileys@2.0.0
- @prototypevip/baileys@0.1.6
- base58-cli@1.0.0
Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.