LWA-2026-13998 confirmed malware

sauruspro-bail@5.3.3

Malicious code in sauruspro-bail (npm)

T1195.002 · Compromise Software Supply ChainT1027 · Obfuscated Files or InformationT1036 · MasqueradingT1071.001 · Web ProtocolsT1105 · Ingress Tool Transfer

Analysis

This WhatsApp (Baileys) fork ships code that silently enlists the installing user's WhatsApp account into channels the publisher controls. In lib/Socket/newsletter.js, inside makeNewsletterSocket — the base factory every socket in the library is built from — a base64 literal decodes to hxxps://push-saurus[.]yorunime[.]sbs/idch[.]json. Ten seconds after a socket is created, the code fetches that URL, parses a JSON list whose entries contain an "idch" array of channel JIDs, and calls the library's own channel-follow routine (Types.QueryIds.FOLLOW) on each one at 5-second intervals, with every error swallowed. The list of channels is served remotely, so the set of subscriptions an account is pushed into can be changed server-side at any time without a new release; nothing about this is exposed in the public API or documentation. In lib/Socket/luxu.js the outgoing status event message is stamped with a hardcoded third-party channel attribution (newsletterName "D | 7eppeli-Exloration", newsletterJid 120363418964199743@newsletter) as forwardedNewsletterMessageInfo, so messages the user sends carry a channel they do not own. The package also declares a dependency on cache-manager ^7.2.8, which resolves to a version of that package previously identified as malicious. Observable indicators: hxxps://push-saurus[.]yorunime[.]sbs/idch[.]json (channels list, fetched on socket creation), channel JID 120363418964199743@newsletter with name "D | 7eppeli-Exloration", and dependency range cache-manager@^7.2.8.

analyzed by
Leitwacht
first seen
Nov 15, 2026, 04:20 AM
analyzed
Nov 15, 2026, 04:20 AM
weekly installs
1,843

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.