Malware in lint-builders
The npm package lint-builders contained malware that provided full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised and all secrets and keys rotated immediately from a different machine.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- lint-builders
The npm package lint-builders was found to contain malware. According to the GitHub Advisory (GHSA-pgr4-r9gw-w9wm), 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 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 package installation, given that the attacker may have gained full control of the system.\n\nThe incident was published on 2026-07-06 via the GitHub Advisory database.
Indicators of compromise
- Packages
- lint-builders
Remediation
- Immediately isolate any computer that has lint-builders installed or running from the network
- Rotate all secrets, API keys, credentials, and signing keys from a different, uncompromised computer
- Remove the lint-builders package from all affected systems
- Conduct a full forensic analysis of affected systems to identify any additional malicious software or persistence mechanisms
- Review all access logs and audit trails for the period during which the package was installed
- Consider full system reimaging as the most reliable remediation given the potential for full system compromise
Sources
- GitHub Advisory GHSA-pgr4-r9gw-w9wm · GitHub Advisory Database
Cite this entry
"Malware in lint-builders." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 6, 2026; last updated July 6, 2026. https://supplychainattack.org/incident/malware-in-lint-builders-i7k6o1
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