Malicious code in @mastra/server (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (3e88fa7d4c9b877f3fe67c78cbefa1ed49532b4dce6fcefa4963db91a32634ea) The package was found to contain malicious code or consuming dependency that contains malicious code ## Source: ghsa-malware (eb94d4509745d002f2de634d4e8b797f831d24b13fa6dae2f41d67ce6441eba9) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
AI Analysis
Technical Summary
The @mastra/server npm package at version 2.1.1 has been identified as containing malicious code or relying on a dependency that contains malicious code. According to the source data from Amazon Inspector and GitHub Security Advisories, any system with this package installed or running should be considered fully compromised. The malicious code presence implies that attackers may have gained full control over the affected system. Immediate remediation involves removing the package and rotating all secrets and keys from a separate secure environment. However, due to the potential persistence of malicious software, removal of the package does not guarantee full eradication of the threat.
Potential Impact
Systems with @mastra/server version 2.1.1 installed or running are fully compromised. Attackers may have complete control over the system, risking exposure or theft of secrets, keys, and sensitive data. The compromise may allow persistent malicious activity beyond the presence of the package itself.
Mitigation Recommendations
Remove the @mastra/server package version 2.1.1 from all affected systems immediately. Rotate all secrets and keys stored on the compromised systems from a separate, secure machine. Because full control may have been given to an attacker, further forensic analysis and system restoration from known good backups are recommended. Patch status is not confirmed; check vendor advisories for updates or safer package versions.
Malicious code in @mastra/server (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (3e88fa7d4c9b877f3fe67c78cbefa1ed49532b4dce6fcefa4963db91a32634ea) The package was found to contain malicious code or consuming dependency that contains malicious code ## Source: ghsa-malware (eb94d4509745d002f2de634d4e8b797f831d24b13fa6dae2f41d67ce6441eba9) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The @mastra/server npm package at version 2.1.1 has been identified as containing malicious code or relying on a dependency that contains malicious code. According to the source data from Amazon Inspector and GitHub Security Advisories, any system with this package installed or running should be considered fully compromised. The malicious code presence implies that attackers may have gained full control over the affected system. Immediate remediation involves removing the package and rotating all secrets and keys from a separate secure environment. However, due to the potential persistence of malicious software, removal of the package does not guarantee full eradication of the threat.
Potential Impact
Systems with @mastra/server version 2.1.1 installed or running are fully compromised. Attackers may have complete control over the system, risking exposure or theft of secrets, keys, and sensitive data. The compromise may allow persistent malicious activity beyond the presence of the package itself.
Mitigation Recommendations
Remove the @mastra/server package version 2.1.1 from all affected systems immediately. Rotate all secrets and keys stored on the compromised systems from a separate, secure machine. Because full control may have been given to an attacker, further forensic analysis and system restoration from known good backups are recommended. Patch status is not confirmed; check vendor advisories for updates or safer package versions.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-6036
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-wm6j-68jc-4x58"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a50ba5c68715ace4357effe
Added to database: 07/10/2026, 09:24:44 UTC
Last enriched: 07/10/2026, 09:45:48 UTC
Last updated: 07/31/2026, 06:59:09 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.