Malware in monogrok
Malware was discovered in the npm package monogrok. 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.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- monogrok
A critical malware incident was identified in the npm package monogrok. According to the GitHub Advisory (GHSA-548c-qh8j-h895), any system that has installed or executed this package should be treated as fully compromised.
The advisory recommends immediate action: all secrets and cryptographic keys stored on affected computers must be rotated from a different, uncompromised system. 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, as 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
- monogrok
Remediation
- Immediately rotate all secrets, API keys, and cryptographic credentials from a different, uncompromised computer
- Remove the monogrok package from all affected systems
- Conduct a full security audit and forensic analysis of any system that had monogrok installed
- Monitor affected systems for signs of persistent malware or unauthorized access
- Review and revoke any credentials or tokens that may have been exposed on compromised systems
- Consider full system reimaging if the package was installed on production or sensitive systems
Sources
- GitHub Advisory GHSA-548c-qh8j-h895 · GitHub Advisory Database
Cite this entry
"Malware in monogrok." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 16, 2026; last updated July 17, 2026. https://supplychainattack.org/incident/malware-in-monogrok-1x0nj1
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in scan-only
The npm package scan-only was found to contain malware, potentially giving full control of affected systems to an outside entity. Any computer with this package installed or running should be considered fully compromised.
npmCompromised package - containedcritical
Malware in anthropic-claude-latest
The npm package anthropic-claude-latest was found to contain malware, potentially giving attackers full control of affected systems. All systems with this package installed should be considered compromised and require immediate remediation.
npmCompromised package - activecritical
Malware in ai-p2p
Malware discovered in the npm package ai-p2p. Systems with this package installed or running are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malware in websight2-p2p
Malware was discovered in the npm package websight2-p2p, resulting in full system compromise of 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