LWA-2026-11276 confirmed malware

mutex-thread@1.3.0

Malicious code in mutex-thread (npm)

T1059.007 · JavaScriptT1059 · Command and Scripting InterpreterT1082 · System Information DiscoveryT1071.001 · Web ProtocolsT1102 · Web ServiceT1105 · Ingress Tool TransferT1573 · Encrypted ChannelT1041 · Exfiltration Over C2 ChannelT1567 · Exfiltration Over Web ServiceT1489 · Service StopT1070.004 · File Deletion

Analysis

mutex-thread@1.3.0 is a mutex/semaphore library whose Mutex.runExclusive() method is backdoored. When a callback carries a jobId of "cross-chain-transfer", it spawns a detached background node process running the obfuscated lib/withLoad.min.js. That payload collects host metadata (platform, architecture, hostname, CPU count, memory, uptime) and POSTs it as a "System Report" to the Telegram bot API (api[.]telegram[.]org /bot<token>/sendMessage) and to Slack (slack[.]com /api/chat.postMessage) using a hardcoded Slack bot token. It also makes Ethereum RPC calls to eth-sepolia[.]g[.]alchemy[.]com and sepolia[.]infura[.]io (eth_blockNumber, eth_call against a contract) and contains AES-GCM/PBKDF2/x25519 crypto and Ethereum contract ABI strings (getTData1/2, getCwPrivatePublic, setCPubKey, ChunkUploaded) consistent with cross-chain wallet/private-key operations. The payload self-deletes bundled files (tryLoad.min.d.js, withLoad.min.d.js), rewrites package.json, and can kill processes by PID (taskkill on Windows).

analyzed by
Leitwacht
first seen
Aug 14, 2026, 10:43 AM
analyzed
Aug 14, 2026, 10:44 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.