Malware in async-mutex-v2
Malware was discovered in the npm package async-mutex-v2. Systems with this package installed are considered fully compromised and require immediate remediation including credential rotation and package removal.
- Disclosed
- Last updated
- Blast radius
- Any system with async-mutex-v2 installed
- Ecosystems
- Attack vectors
- Affected entities
- async-mutex-v2npm package
A malware incident was identified in the npm package async-mutex-v2. According to the GitHub advisory, any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised system. The malicious package should be removed, though there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise.\n\nGiven the critical nature of the compromise and the potential for full system control by an external entity, comprehensive security remediation is required beyond simple package removal.
Indicators of compromise
- Packages
- async-mutex-v2
Remediation
- Immediately rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the async-mutex-v2 package from all affected systems
- Conduct a full security audit of any system that had async-mutex-v2 installed
- Monitor affected systems for signs of persistent malware or unauthorized access
- Review system logs and network traffic for indicators of compromise
- Consider full system reimaging if the package was installed on production or sensitive systems
Sources
- GitHub Advisory GHSA-f829-g84r-2fq7 · GitHub Advisory Database
Cite this entry
"Malware in async-mutex-v2." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 17, 2026; last updated August 17, 2026. https://supplychainattack.org/incident/malware-in-async-mutex-v2-jvgw23
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malicious code in 3-buildsight-web (npm)
The npm package 3-buildsight-web contains malicious code that fetches and executes arbitrary JavaScript from a remote Bitbucket URL on module load, granting full page privileges to an unverified third party.
npmCompromised package - resolvedcritical
Malicious code in @usaa-grp-personal-profile/personal-profile-common (npm)
Malicious package @usaa-grp-personal-profile/personal-profile-common version 999.0.0 published to public npm as a dependency-confusion attack targeting an organization's internal registry. The package contains preinstall and postinstall hooks that exfiltrate hostname, username, and working directory to an attacker-controlled OAST endpoint on every install.
npmDependency confusionCompromised package - resolvedcritical
Malicious code in create-coin (npm)
create-coin@20.1.1 on npm contained malicious postinstall code that collected sensitive environment variables, credentials, and host reconnaissance data. The package impersonated an esbuild platform build and exfiltrated data to a hardcoded endpoint.
npmCompromised packageTyposquatting - resolvedcritical
Malicious code in @syncraft-labs/vue (npm)
The npm package @syncraft-labs/vue version 0.4.1 contained malicious obfuscated code in its ESM build that implements a blockchain-hosted C2 dropper (EtherHiding pattern), enabling remote code execution on any consumer importing the package.
npmCompromised package