Malware in brock-loader
Malware was discovered in the npm package brock-loader, resulting in full system compromise of any computer with the package installed or running. All affected systems should be considered fully compromised and all secrets and keys rotated immediately.
- Disclosed
- Last updated
- Blast radius
- Any system with brock-loader installed or running
- Ecosystems
- Attack vectors
- Affected entities
- brock-loader
The npm package brock-loader was found to contain malware. According to the GitHub advisory (GHSA-gwv3-x257-r43c), any computer that has this package installed or running should be considered fully compromised.\n\nImmediate action is required for all affected systems. All secrets and keys stored on compromised computers should be rotated immediately from a different, unaffected computer. The package should be removed, though there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise.\n\nGiven the critical nature of the compromise and the potential for persistent backdoors or additional malware, a full security audit and potential system rebuild may be necessary for affected systems.
Indicators of compromise
- Packages
- brock-loader
Remediation
- Immediately remove the brock-loader package from all systems
- Rotate all secrets, API keys, and credentials from a different, unaffected computer
- Conduct a full security audit of any system that had brock-loader installed
- Consider rebuilding affected systems from clean media if full compromise is suspected
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Monitor for any unauthorized access attempts using rotated credentials
Sources
- GitHub Advisory GHSA-gwv3-x257-r43c · GitHub Advisory Database
Cite this entry
"Malware in brock-loader." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 30, 2026; last updated June 30, 2026. https://supplychainattack.org/incident/malware-in-brock-loader-199shv
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