robomergenpm
robomerge is a confirmed malicious npm package (MAL-2026-6729) that steals credentials and exfiltrates sensitive data (malicious version 99999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in robomerge (npm)
What this malware does
package.json declares a preinstall lifecycle script that fires automatically on npm install. The script collects installer hostname, username, cwd, platform, arch, node version, npm user-agent, and CI identifiers (HORDE, GitHub Actions, Jenkins, TeamCity), then iterates process.env and selects up to 30 entries whose keys match credential-shaped regexes (AWS_, GITHUB_, GH_, NPM_, EPIC_, UE_, HORDE_, P4, CI, BUILD, TOKEN, KEY, SECRET), including their values. The collected JSON is POSTed over cleartext HTTP to http://109.123.247.172/npm/robomerge. A second exfiltration channel encodes hostname and username into a subdomain of *.robomerge.npm.epic-dc.oast.fun and issues a dns.lookup, providing out-of-band exfiltration that bypasses HTTP egress filters. The package name 'robomerge' combined with env-var targeting of EPIC_, UE_ (Unreal Engine), HORDE_ (Epic's Horde CI), and P4 (Perforce) indicates targeting of Epic Games internal build infrastructure; the sentinel version 99999.0.0 is the dependency-confusion shape used to force public-registry resolution over an internal package of the same name.
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.
The OpenSSF Package Analysis project identified 'robomerge' @ 99999.0.0 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for robomerge (version 99999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging robomerge across your stack and pipelines.
If you installed it — respond
robomerge is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If robomerge was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks robomerge before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks robomerge-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.