unreal-horde-dashboard

Details

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

## Source: amazon-inspector (15cf7eca1e6de1e7ecc5fe67d8094125f20f6ca4256e843b72e89760c97888b8)
unreal-horde-dashboard@99999.0.0 executes a preinstall script that runs automatically on `npm install`. The script collects host identifiers (hostname, username, cwd, platform, node version, npm user-agent) and enumerates process.env, filtering for credential-shaped keys matching /^(AWS_|GITHUB_|GH_|NPM_|EPIC_|UE_|HORDE_|P4|CI|BUILD|TOKEN|KEY|SECRET)/i (up to 30 entries). The collected JSON is POSTed over plain HTTP to a hardcoded bare-IP endpoint at http://109.123.247.172/npm/unreal_horde_dashboard. In parallel it issues a DNS lookup for `<hostname>-<username>.unreal_horde_dashboard.npm.epic-dc.oast.fun`, an interactsh-style out-of-band callback that encodes installer identity into a subdomain and bypasses HTTP egress controls. The package name and env-var probes (HORDE_AGENT, EPIC_, UE_, P4) target Epic Games' Unreal Engine Horde build system, and the 99999.0.0 version is a dependency-confusion signature intended to override an internal package of the same name in Epic's build pipeline. Installing this package on a developer workstation or CI runner leaks AWS, GitHub, npm, Perforce, and Epic/Horde-scoped secrets to the attacker.

## Source: ghsa-malware (3ed46a77bb9ee6410fe6ba2f71dd90cb2037dc2a88bdd98304d18a6a031f1815)
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 (5e9b87fe74bfc9ebca4a6385b3038cd8a3b5d9907b02772377ed3383318578e4)
The OpenSSF Package Analysis project identified 'unreal-horde-dashboard' @ 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.