LWA-2026-13855 MAL-2026-18905 ↗ confirmed malware

@trashcore/baileys@4.1.8

Malicious code in @trashcore/baileys (npm)

T1195.002 · Compromise Software Supply ChainT1098 · Account ManipulationT1027 · Obfuscated Files or Information

Analysis

This package republishes the WhatsApp library `baileys` under an unofficial `@trashcore` scope and its README tells consumers to remap the canonical `@whiskeysockets/baileys` dependency to `npm:@trashcore/baileys@latest`, so installing it silently replaces the branded library. Beyond the clone, it ships an undisclosed auto-follow payload: `lib/Socket/newsletter.js` starts an unconditional timer when the socket is created (90 s, then a second 5 s later) and issues a newsletter `FOLLOW` mutation (query id 7871414976211147) for two hardcoded channel JIDs that are hidden as base64 literals — `MTIwMzYzNDIwMjQ5NjcyMDczQG5ld3NsZXR0` → `120363420249672073@newsletter` and `MTIwMzYzNDI0MDIwMjgzNzU5QG5ld3NsZXR0Z` → `120363424020283759@newsletter` — with every error swallowed by empty catch blocks. Because `makeNewsletterSocket` is invoked from `lib/Socket/messages-send.js` when a send socket is built, any bot using the package enrols its WhatsApp account in the operator's channels without the user's knowledge. A further channel JID (`0@newsletter`, "7eppeli - Information") is hardcoded in `lib/Utils/messages.js`. The package also fetches its protocol version from the mutable third-party file `hxxps://raw[.]githubusercontent[.]com/kiuur/bails/master/src/Defaults/baileys-version[.]json`. No network IOC beyond WhatsApp infrastructure and that raw GitHub path; the malicious behaviour is local account manipulation.

analyzed by
Leitwacht
first seen
Nov 10, 2026, 12:17 AM
analyzed
Nov 10, 2026, 06:02 AM
weekly installs
2,802

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.