NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

mutex-threadnpm

Advisory published Updated

mutex-thread is a confirmed malicious npm package (MAL-2026-14185) that opens a backdoor for remote access (malicious version 1.3.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mutex-thread (npm)

MAL-2026-14185
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall mutex-thread

What this malware does

The package presents itself as a mutex library but lib/Mutex.js contains an injected branch in runExclusive that, when a caller passes callback.meta.jobId === 'cross-chain-transfer', spawns lib/withLoad.min.js as a detached node child with stdio ignored and windowsHide true. lib/withLoad.min.js is a hex/base64-obfuscated dropper that reads an encrypted key from a Sepolia Ethereum smart contract (via eth-sepolia.g.alchemy.com and sepolia.infura.io RPC endpoints), derives a shared secret, decrypts payloads hosted on the contract, writes them to disk, chmods 755, and re-spawns node on them. Before entering its command loop it collects host reconnaissance (os.platform, release, arch, hostname, cpus, totalmem, freemem, uptime) and posts it to a hardcoded Slack bot via slack.com/api/chat.postMessage and to a hardcoded Telegram bot at api.telegram.org/bot<token>/sendMessage. lib/tryLoad.min.d.js polls slack.com/api/conversations.history every ~10 seconds with a hardcoded bearer token and channel id, reassembles chunked messages, AES-GCM-decrypts them using a key passed via argv, writes the plaintext to withLoad.min.js, chmods 755, and spawns node on it; an 'exitexitexit' sentinel triggers self-deletion of loader files and killing of a peer PID. String-array rotation and base64 wrapping are used to hide C2 hosts, bot tokens, channel ids, and the Sepolia contract address.

Malicious versions

1 flagged
1.3.0

Indicators of compromise (SHA-256)

e142539248a690ef78ebe7ceeaa4c16e9903107a04704e1947cf296bce543097

Detection & response playbook

Backdoor / remote access
  1. Find it

    Search your lockfiles and build artifacts for mutex-thread (version 1.3.0).

  2. If you installed it — respond

    mutex-thread establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

  3. Did it already run?

    If mutex-thread was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. mutex-thread on npm has been identified as a malicious package (version 1.3.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018228

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks mutex-thread-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Explore

mutex-thread (npm) malicious package — MAL-2026-14185 | O3 Security