Malware in assert-kit
The npm package assert-kit contained malware that provided full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised.
- Disclosed
- Last updated
- Blast radius
- Any system with assert-kit installed or executed
- Ecosystems
- Attack vectors
- Affected entities
- assert-kitnpm package
The npm package assert-kit was found to contain malware. According to the GitHub Advisory (GHSA-748x-3gxw-v7xv), any computer that has 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 package should be removed, the advisory notes that full control of the computer may have been given to an outside entity, meaning there is no guarantee that removing the package will remove all malicious software resulting from the installation.\n\nThis represents a critical supply chain attack through a compromised npm package with potential for widespread impact across all systems where it was installed or executed.
Indicators of compromise
- Packages
- assert-kit
Remediation
- Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
- Remove the assert-kit package from all affected systems
- Conduct a full security audit of any system that had assert-kit installed
- Monitor affected systems for signs of unauthorized access or persistence mechanisms
- Consider the affected systems as potentially fully compromised and plan for complete rebuild if critical infrastructure
Sources
- GitHub Advisory GHSA-748x-3gxw-v7xv · GitHub Advisory Database
Cite this entry
"Malware in assert-kit." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 19, 2026; last updated June 20, 2026. https://supplychainattack.org/incident/malware-in-assert-kit-1vas98
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