@sakataa/baileys@4.0.1
Malicious code in @sakataa/baileys (npm)
Analysis
A republished WhatsApp bot library ("Sakata Baileys") that forks the well-known baileys codebase and adds two hidden behaviours to the shipped source. Silent channel auto-subscription: lib/Socket/newsletter.js contains a hardcoded array of four BASE64-encoded WhatsApp newsletter JIDs. When the socket is created, timers (10s, 15s, 20s, 25s) fire FOLLOW mutations for each of them (xwa2_newsletter_follow), with errors swallowed in an empty catch. Any bot built on this library silently subscribes the logged-in WhatsApp account to four channels that the developer controls, without the operator calling any API or seeing any log line. The base64 encoding serves only to keep the channel IDs out of plain sight. Phone-number exfiltration: lib/Socket/socket.js exposes a `checkBan(number)` helper that normalises the supplied number and issues a GET to hxxps://kyuux-r[.]indevs[.]in/api/check-whatsapp?phone=<number> with a spoofed desktop browser User-Agent, then returns the remote JSON with a `creator: "t[.]me/luyatiem"` field injected. Every number a bot operator checks with this helper is delivered to an unrelated third party. The package manifest also declares a caret dependency on cache-manager ^7.2.8, which resolves to a compromised release of that package. IOCs: hxxps://kyuux-r[.]indevs[.]in/api/check-whatsapp; hxxps://t[.]me/luyatiem; hxxps://t[.]me/sakata_real; hxxps://t[.]me/infobaileys. Files of interest: lib/Socket/newsletter.js, lib/Socket/socket.js.
- analyzed by
- Leitwacht
- first seen
- Nov 9, 2026, 07:41 AM
- analyzed
- Nov 9, 2026, 08:06 AM
- weekly installs
- 1,458
Related advisories
- @sakataa/baileys@5.0.1 same package
- @sakataa/baileys@5.0.0 same package
- @sakataa/baileys@4.0.2 same package
- @sakataa/baileys@4.0.0 same package
- @sakataa/baileys@1.0.0 same package
- @sakataa/baileys@2.0.0 same package
- smfos-bskdz-util@1.0.1
- jmrwd-gjdob-util@1.0.1
Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.