Malware in mazemap
The npm package mazemap was found to contain malware, resulting in full system compromise of any computer with the package installed or running. All secrets and keys should be rotated immediately from a different computer, and the package should be removed.
- Disclosed
- Last updated
- Blast radius
- Any system with the mazemap package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- mazemap
The npm package mazemap was identified as containing malware. According to the GitHub Advisory (GHSA-xc8q-h68h-r6r9), 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 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 outside entity may have gained full control of the system.\n\nUsers should treat any system that has run this package as potentially fully compromised and take appropriate incident response measures.
Indicators of compromise
- Packages
- mazemap
Remediation
- Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
- Remove the mazemap package from all affected systems
- Conduct a full security audit and forensic analysis of any system that had the package installed or running
- Monitor affected systems for signs of persistent malware or unauthorized access
- Consider rebuilding affected systems from clean media if full compromise is suspected
Sources
- GitHub Advisory GHSA-xc8q-h68h-r6r9 · GitHub Advisory Database
Cite this entry
"Malware in mazemap." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 10, 2026; last updated July 10, 2026. https://supplychainattack.org/incident/malware-in-mazemap-zoac7s
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 motiondnb
Malware was discovered in the npm package motiondnb, 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 - containedcritical
Malware in ng-search-api
Malware was discovered in the npm package ng-search-api. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malware in firefly-utilities-helper
Malware was discovered in the npm package firefly-utilities-helper. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malware in polygon-gamma-apis
Malware was discovered in the npm package polygon-gamma-apis. 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