Malware in vitest-cli
Malware discovered in the npm package vitest-cli. Systems with this package installed or running should be considered fully compromised. All secrets and keys must be rotated from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with vitest-cli installed or executed
- Ecosystems
- Attack vectors
- Affected entities
- vitest-clinpm package
A critical malware incident was identified in the npm package vitest-cli. According to the GitHub Advisory (GHSA-c35r-fwrq-cgq9), any computer that has installed or executed this package should be considered fully compromised.\n\nThe advisory recommends immediate rotation of all secrets and keys stored on affected systems from a different, uncompromised computer. 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.\n\nThis represents a severe supply chain attack through a compromised npm package with potential for complete system takeover.
Indicators of compromise
- Packages
- vitest-cli
Remediation
- Immediately isolate any system that has vitest-cli installed or has executed it
- Rotate all secrets, API keys, credentials, and signing keys from a different, uncompromised computer
- Remove the vitest-cli package from all affected systems
- Conduct a full forensic analysis of affected systems to identify any additional malicious software
- Review all code commits and deployments made from affected systems for potential tampering
- Monitor for unauthorized access or activity on accounts that may have been compromised
Sources
- GitHub Advisory GHSA-c35r-fwrq-cgq9 · GitHub Advisory Database
Cite this entry
"Malware in vitest-cli." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 23, 2026; last updated June 23, 2026. https://supplychainattack.org/incident/malware-in-vitest-cli-0hkkxc
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in autbank-core (npm)
The npm package autbank-core contained malicious preinstall and postinstall lifecycle hooks that exfiltrated environment variables, credentials, and system information to a hardcoded webhook.site endpoint during installation.
npmCompromised package - resolvedcritical
Malicious code in adxaa (npm)
The npm package adxaa contained obfuscated malicious JavaScript designed to target users of a specific WordPress site. The payload exfiltrates session data, deletes accounts, and hijacks credentials via email overwrite and password reset.
npmCompromised package - resolvedcritical
Malicious code in upload-to-gcp (npm)
upload-to-gcp@3.2.1 (npm) contains malicious code in its postinstall script that exfiltrates host identifiers to an attacker-controlled endpoint. The package masquerades as a Google Cloud Platform utility but performs unauthorized telemetry collection at install time.
npmCompromised package - resolvedcritical
Malicious code in akamai-sensor (npm)
A malicious npm package named akamai-sensor impersonated Akamai's legitimate sensor_data anti-bot SDK. The package contained hidden JavaScript code concealed using invisible Unicode characters and implemented a dynamic command-and-control channel via a Google Calendar dead-drop, enabling arbitrary code execution on installation.
npmCompromised packageTyposquatting