Malware in resolve-audit
The npm package resolve-audit was compromised and distributed with malware. Any system with the package installed or running should be considered fully compromised and all secrets/keys rotated immediately from a different machine.
- Disclosed
- Last updated
- Blast radius
- Any system with resolve-audit installed or executed
- Ecosystems
- Attack vectors
- Affected entities
- resolve-auditnpm package containing malware
The npm package resolve-audit was found to contain malware. According to the GitHub Advisory (GHSA-69qf-g8jq-47xv), any computer that has this package installed or running should be considered fully compromised.
The advisory recommends immediate rotation of all secrets and keys stored on affected computers from a different, uncompromised machine. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the compromise.
This represents a critical supply chain attack through a compromised npm package with potential for complete system compromise.
Indicators of compromise
- Packages
- resolve-audit
Remediation
- Immediately rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the resolve-audit package from all affected systems
- Audit system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical infrastructure
- Check for any other suspicious packages or modifications on affected systems
- Monitor for any lateral movement or persistence mechanisms that may have been installed
Sources
- GitHub Advisory GHSA-69qf-g8jq-47xv · GitHub Advisory Database
Cite this entry
"Malware in resolve-audit." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 18, 2026; last updated August 18, 2026. https://supplychainattack.org/incident/malware-in-resolve-audit-5n35c8
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in chlklib
Malware was discovered in the npm package chlklib, resulting in full system compromise of any computer with the package installed or running. All affected systems should be considered fully compromised and all secrets and keys rotated immediately from a different computer.
npmCompromised package - resolvedcritical
Malware in alphazone
The npm package alphazone contained malware that provided full system compromise to attackers. Any computer with the package installed or running should be considered fully compromised.
npmCompromised package - containedcritical
Malware in chai-as-deployer
Malware was discovered in the npm package chai-as-deployer, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.
npmCompromised package - containedcritical
Malware in checkout-common-tokens
Malware was discovered in the npm package checkout-common-tokens. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package