Malware in robomerge
Malware was discovered in the robomerge npm package. Systems with the package installed or running should be considered fully compromised, requiring immediate rotation of all secrets and keys from a clean system.
- Disclosed
- Last updated
- Blast radius
- Any system with robomerge installed or running
- Ecosystems
- Attack vectors
- Affected entities
- robomergenpm package
A critical malware incident was identified in the robomerge npm package. According to the GitHub advisory, any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate action: all secrets and keys stored on affected computers should be rotated immediately 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, given that the outside entity may have gained full control of the system.\n\nAffected users should treat any system that has run robomerge as potentially containing persistent malware and take appropriate incident response measures.
Indicators of compromise
- Packages
- robomerge
Remediation
- Immediately rotate all secrets, API keys, and credentials from a clean, uncompromised system
- Remove the robomerge package from all affected systems
- Conduct a full security audit and malware scan of any system that had robomerge installed or running
- Review system logs and access logs for any unauthorized activity during the period robomerge was installed
- Consider the affected system(s) as potentially compromised and plan for full rebuild or forensic analysis
- Notify any services or systems that may have been accessed from the compromised system
Sources
- GitHub Advisory GHSA-x22f-73cv-vccx · GitHub Advisory Database
Cite this entry
"Malware in robomerge." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 10, 2026; last updated July 10, 2026. https://supplychainattack.org/incident/malware-in-robomerge-1afhsq
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 svelte-dim-kit
The npm package svelte-dim-kit was found to contain malware, potentially giving attackers full control of affected systems. All systems with this package installed should be considered compromised and secrets/keys rotated immediately from a different computer.
npmCompromised package - containedcritical
Malicious code in @syncraft-labs/react (npm)
The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.
npmCompromised package - containedcritical
Malicious code in stillm4ddpocs-demo-sprocket (npm)
The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.
npmCompromised packageDependency confusion - resolvedcritical
Malicious code in stillm4ddpocs-rtest-bravo (npm)
The npm package stillm4ddpocs-rtest-bravo contained malicious code in its preinstall script that automatically executed during installation, collecting system information and internal package metadata and exfiltrating it to a third-party Interactsh collector via HTTPS and DNS tunneling.
npmCompromised package