Malware in @mastra/e2b
Malware discovered in the npm package @mastra/e2b. 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/e2b
A critical malware incident was identified in the npm package @mastra/e2b. According to the GitHub Security Advisory (GHSA-jg9x-69gr-j4hh), 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 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 compromise.\n\nThe package should be considered a supply chain attack vector affecting all downstream users and systems that depend on @mastra/e2b.
Indicators of compromise
- Packages
- @mastra/e2b
Remediation
- Immediately remove the @mastra/e2b package from all systems
- Rotate all secrets, API keys, and cryptographic credentials from a different, uncompromised computer
- Conduct a full security audit of any system that had this package installed
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider the affected system(s) as potentially fully compromised and plan for forensic analysis or rebuild
- Notify all downstream users and services that depend on @mastra/e2b
Sources
- GitHub Advisory GHSA-jg9x-69gr-j4hh · GitHub Advisory Database
Cite this entry
"Malware in @mastra/e2b." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 17, 2026; last updated June 20, 2026. https://supplychainattack.org/incident/malware-in-mastra-e2b-149m5b
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- activecritical
Malware in internallib_v688
Malware discovered in the npm package internallib_v688. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malicious code in @zzzgenesis00/bip39-generator (npm)
The npm package @zzzgenesis00/bip39-generator version 3.1.2 was identified as malicious by the OpenSSF Package Analysis project. The package communicates with a domain associated with malicious activity.
npmCompromised package - containedcritical
Malware in accounts-final-form
The npm package accounts-final-form contained malware, potentially giving outside entities full control of affected systems. All systems with this package installed should be considered fully compromised.
npmCompromised package - containedcritical
Malicious code in simple-date-formatter-new-1 (npm)
The npm package simple-date-formatter-new-1 version 1.0.0 was identified as malicious by the OpenSSF Package Analysis project. The package communicates with domains associated with malicious activity and executes commands associated with malicious behavior.
npmCompromised package