The mutex-forge npm package masquerades as a mutex/semaphore library but contains a hidden multi-stage malicious loader. When triggered by a specific callback, it collects detailed host information and sends it to attacker-controlled Telegram and Slack channels using embedded bot tokens. It connects to the Ethereum Sepolia network to retrieve encrypted payloads from a smart contract, decrypts them using AES-GCM with an X25519-derived key, writes them to disk, and executes them. A persistent remote command channel is established by polling Slack API for attacker commands, decrypting and executing them. The malware cleans up by deleting its loader files and rewriting its source code to remove the malicious trigger, attempting to evade detection. Live third-party bot tokens and network destinations are embedded in obfuscated form within the payload.

Systems with mutex-forge versions 2.0.0, 2.0.1, or 2.0.2 installed are fully compromised. The attacker gains remote code execution, persistent control, and exfiltration capabilities. All secrets and keys on the compromised system should be considered exposed and rotated immediately. Removing the package alone does not guarantee removal of all malicious components due to the persistence mechanisms employed.

No official patch or fix is currently available for this malicious package. Immediate removal of mutex-forge versions 2.0.0, 2.0.1, and 2.0.2 is strongly recommended. All credentials and secrets stored on affected systems should be rotated from a secure, uncompromised environment. Due to the persistence and cleanup behavior of the malware, a full system compromise should be assumed, and affected systems should be thoroughly investigated and rebuilt if necessary.