LWA-2026-13878 confirmed malware

@charape/baileys@1.0.7

Malicious code in @charape/baileys (npm)

T1195.002 · Compromise Software Supply ChainT1059.007 · JavaScriptT1552.001 · Credentials In FilesT1071.001 · Web ProtocolsT1102 · Web ServiceT1567 · Exfiltration Over Web Service

Analysis

@charape/baileys is a modified build of the baileys WhatsApp Web library published under a scope that is not the upstream baileys project. It silently enrols the user's WhatsApp account into a channel controlled by the package author. lib/Defaults/index.js ships autoFollow set to 120363424530330931@newsletter, newsletterJid set to the same JID, newsletterName "メ Informasi Store Cԋαɾαρҽ" and channelUrl hxxps://whatsapp[.]com/channel/0029Vb6cCfP3GJP6g8eeff1o. lib/Socket/newsletter.js builds its follow list from config.autoFollow and, on every connection.update event where connection === "open", fires followChannels twice (2.5s and 7s after the socket connects), issuing the xwa2_newsletter_follow mutation for the hardcoded JID with three attempts and 2.5s backoff — a socket created with default options therefore subscribes the victim's account to that channel. lib/Socket/messages-send.js (injectNewsletterWatermark) and lib/Utils/messages.js (prepareWAMessageMedia) additionally stamp a newsletter annotation/watermark referencing the same channel onto outgoing image and video messages, so the channel is advertised through messages the account sends. Media upload failures fall back to posting the user's media buffers to hxxps://catbox[.]moe/user/api[.]php and hxxps://tmpfiles[.]org/api/v1/upload. The package ships no install-time hook and no obfuscated code; its WhatsApp session credentials in creds.json are read and written by the bundled multi-file auth store (lib/Utils/use-multi-file-auth-state.js).

analyzed by
Leitwacht
first seen
Nov 10, 2026, 04:21 AM
analyzed
Nov 10, 2026, 06:06 AM

Related advisories

browse all confirmed advisories →

Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.