Malware in chai-guard
Malware discovered in the npm package chai-guard. Any computer with this package installed or running should be considered fully compromised. All secrets and keys stored on affected systems should be rotated immediately from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with chai-guard installed or running is considered fully compromised; all secrets and keys require rotation.
- Ecosystems
- Attack vectors
- Affected entities
- chai-guardnpm package
The npm package chai-guard has been identified as containing malware. According to the GitHub Advisory (GHSA-29vw-5q5r-8jpw), any computer that has this package installed or running should be considered fully compromised.\n\nImmediate action is required: all secrets and keys stored on affected computers must be rotated immediately from a different, uncompromised computer. The package should be removed, but full system compromise cannot be ruled out.\n\nDue to the potential for complete system takeover, removing the package alone may not eliminate all malicious software that resulted from its installation. A comprehensive security review and potential system rebuild may be necessary.
Indicators of compromise
- Packages
- chai-guard
Remediation
- Immediately rotate all secrets and keys from a different, uncompromised computer
- Remove the chai-guard package from all affected systems
- Conduct a comprehensive security audit of all systems that had chai-guard installed
- Consider full system rebuild or forensic analysis for critical systems
- Review all access logs and activity on affected systems for signs of unauthorized access
- Monitor for any indicators of compromise or data exfiltration
Sources
- GitHub Advisory GHSA-29vw-5q5r-8jpw · GitHub Advisory Database
Cite this entry
"Malware in chai-guard." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 6, 2026; last updated July 6, 2026. https://supplychainattack.org/incident/malware-in-chai-guard-1lt3la
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 test2221 (npm)
The npm package test2221 version 2.2.4 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.
npmCompromised package - containedcritical
Malware in n8n-nodes-trust-me-im-totally-safe
Malware was discovered in the npm package n8n-nodes-trust-me-im-totally-safe, 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 - activecritical
Malware in litespeed-cache
Malware discovered in the npm package litespeed-cache. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.
npmCompromised package - containedcritical
Malware in open-worker-cli
Malware was discovered in the npm package open-worker-cli. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.
npmCompromised package