LWA-2026-13671 confirmed malware

@bellaxchan/eleventech@0.0.8

Malicious code in @bellaxchan/eleventech (npm)

T1195.002 · Compromise Software Supply ChainT1071.001 · Web ProtocolsT1041 · Exfiltration Over C2 ChannelT1082 · System Information Discovery

Analysis

This package is a modified WhatsApp WebSocket client library (a fork of the Baileys protocol stack) that ships non-standard behaviour beyond its stated API and carries a tainted dependency range. Its send path includes an extra module, lib/Socket/luxu.js (class "imup", imported and constructed inside sendMessage in lib/Socket/messages-send.js), which intercepts payment, product, album, event, poll-result, order, group-status and group-label sends and stamps every constructed message with the library author's own WhatsApp channel identifiers (newsletter JIDs 120363421563597486@newsletter and 120363399602691477@newsletter) through forwardedNewsletterMessageInfo, so messages sent with this library carry third-party channel branding; the same module emits a custom GROUP_MEMBER_LABEL_CHANGE protocol node for group labels. Separately, lib/Socket/socket.js exports a checkBan() helper that issues a GET to hxxps://kyuux-r[.]indevs[.]in/api/check-whatsapp with a supplied phone number and a spoofed browser User-Agent, sending contact phone numbers to an undocumented third-party service and merging its response with an author handle. The package also declares a dependency range on cache-manager (^7.2.8) that resolves to 7.2.10, a compromised release, so installing it pulls in a malicious transitive dependency. The preinstall hook (engine-requirements.js) only enforces Node.js >= 20. No obfuscation, dynamic code evaluation, credential/token harvesting or download-and-execute behaviour was found in the shipped code.

analyzed by
Leitwacht
first seen
Nov 5, 2026, 05:21 AM
analyzed
Nov 5, 2026, 05:22 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.