unreal-horde-dashboardnpm
unreal-horde-dashboard is a confirmed malicious npm package (MAL-2026-6732) 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 unreal-horde-dashboard (npm)
What this malware does
[email protected] 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.
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 'unreal-horde-dashboard' @ 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 unreal-horde-dashboard (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 unreal-horde-dashboard across your stack and pipelines.
If you installed it — respond
unreal-horde-dashboard 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 unreal-horde-dashboard 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 unreal-horde-dashboard 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 unreal-horde-dashboard-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.