Malware in @mastra/mcp-registry-registry
Malware was discovered in the npm package @mastra/mcp-registry-registry. 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
- @mastra/mcp-registry-registry
A critical malware incident was identified in the npm package @mastra/mcp-registry-registry. According to the GitHub Security Advisory (GHSA-5w62-p653-57mf), any system that has installed or executed this package should be treated as fully compromised.\n\nThe 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.\n\nAffected users should assume complete system compromise and take appropriate incident response measures.
Indicators of compromise
- Packages
- @mastra/mcp-registry-registry
Remediation
- Immediately rotate all secrets, API keys, and cryptographic credentials from a different, uncompromised computer
- Remove the @mastra/mcp-registry-registry package from all affected systems
- Conduct a full security audit and forensic analysis of any system that had this package installed
- Monitor affected systems for signs of persistent malware or unauthorized access
- Review access logs and audit trails for any suspicious activity during the period the package was installed
- Consider full system reimaging if the package was installed on production or sensitive systems
Sources
- GitHub Advisory GHSA-5w62-p653-57mf · GitHub Advisory Database
Cite this entry
"Malware in @mastra/mcp-registry-registry." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 17, 2026; last updated June 20, 2026. https://supplychainattack.org/incident/malware-in-mastra-mcp-registry-registry-1xn18d
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 ethereum-gas-reporter
Malware was discovered in the ethereum-gas-reporter npm package. Any computer with this package installed or running should be considered fully compromised, requiring immediate rotation of all secrets and keys from a different system.
npmCompromised package - containedcritical
Malware in eth-util
Malware was discovered in the eth-util npm package. Any computer with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different system.
npmCompromised package - containedcritical
Malware in ts-big-ecro
The npm package ts-big-ecro contained malware that fully compromised any system where it was installed. All secrets and keys on affected systems should be rotated immediately, and the package should be removed.
npmCompromised package - containedcritical
Malware in ts-esys
Malware was discovered in the npm package ts-esys. Systems with this package installed or running are considered fully compromised and require immediate remediation.
npmCompromised package