Malware in @mastra/blaxel
Malware was discovered in the npm package @mastra/blaxel. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @mastra/blaxel
A critical malware incident was identified in the npm package @mastra/blaxel, published via GitHub Advisory GHSA-jr4h-q66m-r9c7 on June 17, 2026.\n\nAccording to the advisory, any computer that has this package installed or running should be considered fully compromised. The malware grants full control of the affected system to an outside entity.\n\nImmediate remediation requires rotating all secrets and keys stored on affected computers 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.\n\nUsers should assume complete system compromise and take appropriate incident response measures.
Indicators of compromise
- Packages
- @mastra/blaxel
Remediation
- Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
- Remove the @mastra/blaxel package from all affected systems
- Assume full system compromise and conduct thorough forensic analysis
- Monitor affected systems for signs of persistent malware or backdoors
- Review system logs and network traffic for indicators of compromise
- Consider rebuilding affected systems from clean media if critical infrastructure is involved
Sources
- GitHub Advisory GHSA-jr4h-q66m-r9c7 · GitHub Advisory Database
Cite this entry
"Malware in @mastra/blaxel." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 17, 2026; last updated June 20, 2026. https://supplychainattack.org/incident/malware-in-mastra-blaxel-16upp8
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in test2221 (npm)
The npm package test2221 version 2.2.4 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.
npmCompromised package - containedcritical
Malware in n8n-nodes-trust-me-im-totally-safe
Malware was discovered in the npm package n8n-nodes-trust-me-im-totally-safe, resulting in full system compromise for 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 - activecritical
Malware in litespeed-cache
Malware discovered in the npm package litespeed-cache. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.
npmCompromised package - containedcritical
Malware in open-worker-cli
Malware was discovered in the npm package open-worker-cli. 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