Malware in nolimit-agent
Malware was discovered in the nolimit-agent npm package. Systems with this package installed are considered fully compromised and require immediate remediation including secret rotation and package removal.
- Disclosed
- Last updated
- Blast radius
- Any system with nolimit-agent installed or running
- Ecosystems
- Attack vectors
- Affected entities
- nolimit-agent
The nolimit-agent npm package was found to contain malware. According to the GitHub Advisory (GHSA-f9mj-p83x-395v), 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 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\nUsers should treat any system that has run this package as potentially containing persistent malware and take appropriate containment and recovery measures.
Indicators of compromise
- Packages
- nolimit-agent
Remediation
- Immediately rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the nolimit-agent package from all affected systems
- Perform a full security audit and malware scan of any system that had this package installed
- Consider the affected system(s) as potentially compromised and plan for full remediation or replacement
- Review access logs and audit trails for any unauthorized activity on systems that ran this package
Sources
- GitHub Advisory GHSA-f9mj-p83x-395v · GitHub Advisory Database
Cite this entry
"Malware in nolimit-agent." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 13, 2026; last updated August 13, 2026. https://supplychainattack.org/incident/malware-in-nolimit-agent-11mgvw
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malicious code in runtime-health (npm)
The npm package runtime-health version 1.0.2 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.
npmCompromised package - containedcritical
Malware in blastradar
Malware was discovered in the npm package blastradar, 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 sui-move-graphql
Malware was discovered in the npm package sui-move-graphql. Systems with this package installed or running should be considered fully compromised, requiring immediate rotation of all secrets and keys from a different computer.
npmCompromised package - resolvedcritical
Malware in ulebkit
The npm package ulebkit contained malware that provided full system compromise to attackers. Any computer with the package installed or running should be considered fully compromised.
npmCompromised package