ue-automation-scripts

Details

---
_-= Per source details. Do not edit below this line.=-_

## Source: amazon-inspector (cbc2db9a2a365d53d76fe7ca2a8f219f98118d99b53698cf7ce8b31cf81eda3f)
Package name 'ue-automation-scripts' with version 99999.0.0 is the canonical dependency-confusion shape used to hijack installs on internal CI systems that resolve unqualified names against the public npm registry. The preinstall lifecycle script in package.json runs unconditionally on `npm install` and: (1) collects hostname, username, cwd, platform, node version, npm user-agent, and CI indicators; (2) enumerates process.env with a regex matching credential-shaped keys (AWS_, GITHUB_, GH_, NPM_, EPIC_, UE_, HORDE_, P4, CI, BUILD, TOKEN, KEY, SECRET), taking up to 30 matches; (3) POSTs the JSON payload over plain HTTP to the hardcoded bare-IP endpoint http://109.123.247.172/npm/ue_automation_scripts; and (4) performs a DNS lookup encoding hostname and username as a subdomain of ue_automation_scripts.npm.epic-dc.oast.fun (an interactsh/OAST out-of-band interaction service) as a secondary confirmation channel that also works from environments blocking HTTP egress. The Epic/UE/HORDE/P4 targeting indicates the campaign is aimed at Epic Games / Unreal Engine internal build infrastructure (Horde agents, Perforce credentials).

## Source: ghsa-malware (99a6158ac008e16c5150e5cebe3ffa1da95ae8fa9b5391913e75af12c2611f69)
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 (312f2d385743023503ed2c86bab1361eff17db32aa8a33d6d4da0015b3650095)
The OpenSSF Package Analysis project identified 'ue-automation-scripts' @ 99999.0.0 (npm) as malicious.

It is considered malicious because:

- The package communicates with a domain associated with malicious activity.

Compromised versions (1)

• 99999.0.0

Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.