Malware in mermaid-v11
Malware discovered in the npm package mermaid-v11. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with mermaid-v11 installed or running
- Ecosystems
- Attack vectors
- Affected entities
- mermaid-v11npm package
A critical malware incident has been identified in the npm package mermaid-v11. According to the GitHub Security Advisory (GHSA-xmj9-vhj4-8q6c), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory indicates that all secrets and keys stored on affected computers should be rotated immediately from a different, uncompromised system. While the package should be removed, the advisory notes that full control of the computer may have been given to an outside entity, meaning removal of the package alone may not eliminate all malicious software that resulted from the installation.\n\nThis represents a critical supply chain attack through a compromised npm package with severe implications for all systems that have installed or executed it.
Indicators of compromise
- Packages
- mermaid-v11
Remediation
- Immediately isolate any system with mermaid-v11 installed from the network
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the mermaid-v11 package from all affected systems
- Perform a full security audit and malware scan on affected systems
- Review system logs and access logs for signs of unauthorized activity
- Consider full system reimaging if compromise is confirmed
- Audit any systems that may have been accessed from compromised machines
Sources
- GitHub Advisory GHSA-xmj9-vhj4-8q6c · GitHub Advisory Database
Cite this entry
"Malware in mermaid-v11." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 15, 2026; last updated June 16, 2026. https://supplychainattack.org/incident/malware-in-mermaid-v11-9hrqmt
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