Malware in @keyv/memcache
Malware was discovered in the npm package @keyv/memcache. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with @keyv/memcache installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @keyv/memcache
A critical malware incident was identified in the npm package @keyv/memcache. According to the GitHub Advisory (GHSA-94wj-9g85-8vc8), 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. While the malicious 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 initial compromise, given that the attacker may have gained full control of the system.\n\nThis is a supply chain attack via a compromised package in the npm ecosystem, affecting any user or system that installed or ran @keyv/memcache.
Indicators of compromise
- Packages
- @keyv/memcache
Remediation
- Immediately isolate affected systems from the network
- Rotate all secrets, API keys, and credentials from a clean, uncompromised computer
- Remove the @keyv/memcache package from all affected systems
- Perform a full security audit and malware scan of affected systems
- Review system logs and access logs for signs of unauthorized activity
- Consider full system reimaging if compromise is confirmed
- Notify all users and systems that may have been affected by this compromise
Sources
- GitHub Advisory GHSA-94wj-9g85-8vc8 · GitHub Advisory Database
Cite this entry
"Malware in @keyv/memcache." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 4, 2026; last updated August 4, 2026. https://supplychainattack.org/incident/malware-in-keyv-memcache-jdbfx9
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 @servicetitan/table
Malware was discovered in the npm package @servicetitan/table. Systems with this package installed or running should be considered fully compromised, requiring immediate rotation of all secrets and keys from a separate, unaffected computer.
npmCompromised package - containedcritical
Malware in @servicetitan/standalone-root
Malware was discovered in the npm package @servicetitan/standalone-root, resulting in full system compromise for any computer with the package installed or running. The advisory recommends immediate removal of the package and rotation of all secrets and keys from a different computer.
npmCompromised package - containedcritical
Malware in @servicetitan/anvil2-mcp
Malware was discovered in the npm package @servicetitan/anvil2-mcp. Any computer with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
npmCompromised package - containedcritical
Malware in @servicetitan/docs-uikit
Malware was discovered in the npm package @servicetitan/docs-uikit. Any computer with this package installed or running should be considered fully compromised, requiring immediate rotation of all secrets and keys from a different system.
npmCompromised package