LWA-2026-14076 confirmed malware

@wanzforme/bails@5.0.0

Malicious code in @wanzforme/bails (npm)

T1195.002 · Compromise Software Supply ChainT1059.007 · JavaScriptT1071.001 · Web ProtocolsT1102 · Web ServiceT1041 · Exfiltration Over C2 Channel

Analysis

@wanzforme/bails@5.0.0 is a fork of the Baileys WhatsApp Web library that has been modified to silently enrol any connected account into a hardcoded WhatsApp channel. In lib/Socket/newsletter.js, makeNewsletterSocket() iterates a hardcoded base64 constant (decoding to 120363380357951328@newsletter) and, ~10 seconds after the socket is created (then every 5s per entry), issues a newsletter FOLLOW query (QueryIds.FOLLOW / XWAPaths.xwa2_newsletter_follow) for that channel inside an empty try/catch. The subscription is not configurable and is triggered by ordinary library use, not by any caller action. lib/Socket/luxu.js hardcodes the same channel into forwardedNewsletterMessageInfo (newsletterName "Wanz Lonely", newsletterJid "120363380357951328@newsletter") for relayed event and poll-result messages, and that relay path synthesises the sender JID from a locally generated message id, so messages are presented as forwarded channel content from a fabricated sender. lib/Socket/socket.js also exposes a checkBan() helper that sends phone numbers to hxxps://kyuux-r[.]indevs[.]in/api/check-whatsapp and stamps the returned data with creator "t[.]me/luyatiem"; lib/Utils/check-whatsapp-ban.js wraps the same third-party endpoint at kyuux-r.indevs.in. IOCs: domain kyuux-r.indevs.in; URL hxxps://kyuux-r.indevs.in/api/check-whatsapp; WhatsApp channel JID 120363380357951328@newsletter (base64 MTIwMzYzMzgwMzU3OTUxMzI4QG5ld3NsZXR0ZXI=); Telegram contact t[.]me/luyatiem; channel display name "Wanz Lonely".

analyzed by
Leitwacht
first seen
Nov 14, 2026, 04:36 AM
analyzed
Nov 15, 2026, 11:15 PM
weekly installs
531

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.