Malware in frontend-regulations
The npm package frontend-regulations contained malware that provided full system compromise to attackers. Any computer with this package installed 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
- frontend-regulations
The npm package frontend-regulations was found to contain malware. According to the GitHub Advisory (GHSA-hf3r-x49q-fxm2), any computer that has this package installed or running should be considered fully compromised.
The advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised computer. While the malicious 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.
Users should assume complete system compromise and take appropriate incident response measures.
Indicators of compromise
- Packages
- frontend-regulations
Remediation
- Immediately isolate any computer that has frontend-regulations installed from the network
- Rotate all secrets, API keys, credentials, and signing keys from a different, uncompromised computer
- Remove the frontend-regulations package from all affected systems
- Perform a full forensic analysis and malware scan on affected systems
- Review all access logs and audit trails for suspicious activity during the period the package was installed
- Consider full system rebuild if the package was installed on production or sensitive systems
Sources
- GitHub Advisory GHSA-hf3r-x49q-fxm2 · GitHub Advisory Database
Cite this entry
"Malware in frontend-regulations." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 31, 2026; last updated August 1, 2026. https://supplychainattack.org/incident/malware-in-frontend-regulations-npbo2v
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malware in test-dev-exec
The npm package test-dev-exec contained malware that provided full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised.
npmCompromised package - resolvedcritical
Malware in test-dev-link
Malware was discovered in the npm package test-dev-link. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.
npmCompromised package - resolvedcritical
Malware in @moxfive-llc/common
Malware was discovered in the npm package @moxfive-llc/common. Any computer with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
npmCompromised package - resolvedcritical
Malware in test-dev-dispatch
Malware was discovered in the npm package test-dev-dispatch. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.
npmCompromised package