robomerge

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.