Malicious code in robomerge (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (7b8f632bbc34b020f78b4dec06ddf1bc50194ce117dfe609484d05edc76d7790) 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. ## Source: ghsa-malware (a583e61eec54350bc2e41b3cf740ec606234c0d93b9f8edc901a895718d246ec) 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. ## Source: ossf-package-analysis (55684448bbccf72279c32f468fcfcb8a65500ffd2fe3807aec3e34bfc381a773) 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.
AI Analysis
Technical Summary
The 'robomerge' npm package at version 99999.0.0 includes a preinstall lifecycle script that automatically executes on npm install. This script collects detailed system and environment data such as hostname, username, current working directory, platform, architecture, Node.js version, npm user-agent, and continuous integration environment identifiers (e.g., HORDE, GitHub Actions, Jenkins, TeamCity). It further scans environment variables for keys matching credential-related patterns (e.g., AWS_, GITHUB_, GH_, NPM_, EPIC_, UE_, HORDE_, P4, CI, BUILD, TOKEN, KEY, SECRET) and collects up to 30 such entries with their values. The collected data is sent in cleartext HTTP POST requests to a malicious IP address (http://109.123.247.172/npm/robomerge). Additionally, it performs DNS lookups with encoded data in subdomains to exfiltrate information out-of-band, bypassing HTTP egress filters. The package name and targeted environment variables indicate a focus on Epic Games' internal build infrastructure. The version number 99999.0.0 is used to force resolution from the public npm registry over any internal package of the same name. The package is considered fully malicious and compromises any system where it is installed.
Potential Impact
Installation of this package results in exfiltration of sensitive environment variables and system information, potentially including credentials and secrets used in build and CI environments. This can lead to full system compromise and unauthorized access to internal infrastructure. Secrets and keys stored on the compromised system should be considered exposed and require immediate rotation. Removal of the package alone does not guarantee remediation due to potential persistent compromise.
Mitigation Recommendations
No official patch or fix is available for this malicious package. The recommended mitigation is immediate removal of the 'robomerge' package version 99999.0.0 from all systems. All secrets and credentials exposed on affected systems must be rotated immediately from a secure, uncompromised environment. Systems where this package was installed should be treated as fully compromised, and a thorough incident response investigation is advised.
Malicious code in robomerge (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (7b8f632bbc34b020f78b4dec06ddf1bc50194ce117dfe609484d05edc76d7790) 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. ## Source: ghsa-malware (a583e61eec54350bc2e41b3cf740ec606234c0d93b9f8edc901a895718d246ec) 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. ## Source: ossf-package-analysis (55684448bbccf72279c32f468fcfcb8a65500ffd2fe3807aec3e34bfc381a773) 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.
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 'robomerge' npm package at version 99999.0.0 includes a preinstall lifecycle script that automatically executes on npm install. This script collects detailed system and environment data such as hostname, username, current working directory, platform, architecture, Node.js version, npm user-agent, and continuous integration environment identifiers (e.g., HORDE, GitHub Actions, Jenkins, TeamCity). It further scans environment variables for keys matching credential-related patterns (e.g., AWS_, GITHUB_, GH_, NPM_, EPIC_, UE_, HORDE_, P4, CI, BUILD, TOKEN, KEY, SECRET) and collects up to 30 such entries with their values. The collected data is sent in cleartext HTTP POST requests to a malicious IP address (http://109.123.247.172/npm/robomerge). Additionally, it performs DNS lookups with encoded data in subdomains to exfiltrate information out-of-band, bypassing HTTP egress filters. The package name and targeted environment variables indicate a focus on Epic Games' internal build infrastructure. The version number 99999.0.0 is used to force resolution from the public npm registry over any internal package of the same name. The package is considered fully malicious and compromises any system where it is installed.
Potential Impact
Installation of this package results in exfiltration of sensitive environment variables and system information, potentially including credentials and secrets used in build and CI environments. This can lead to full system compromise and unauthorized access to internal infrastructure. Secrets and keys stored on the compromised system should be considered exposed and require immediate rotation. Removal of the package alone does not guarantee remediation due to potential persistent compromise.
Mitigation Recommendations
No official patch or fix is available for this malicious package. The recommended mitigation is immediate removal of the 'robomerge' package version 99999.0.0 from all systems. All secrets and credentials exposed on affected systems must be rotated immediately from a secure, uncompromised environment. Systems where this package was installed should be treated as fully compromised, and a thorough incident response investigation is advised.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-6729
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a46ecad27e9c7971943b890
Added to database: 07/02/2026, 22:56:45 UTC
Last enriched: 07/10/2026, 11:45:00 UTC
Last updated: 07/24/2026, 10:57:10 UTC
Views: 23
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.