Malicious code in ue-jenkins-buildkite (npm)
MAL-2026-6731 · GHSA-8gxq-wrp7-qqv8
Published · Modified
Dependency scanning
Check whether ue-jenkins-buildkite is in your codebase
Corgea flags malicious and compromised dependencies with reachability analysis, so you fix the packages that actually run in your application instead of working through the whole lockfile.
Description
__
Source: amazon-inspector (f3f4ff9ea00766589ae9dece7648aa4ce29ac9bc82173fce0a1adefaeb6c8f5a)
ue-jenkins-buildkite@99999.0.0 is a dependency-confusion package targeting an internal Epic Games / Unreal Engine CI namespace (name evokes Jenkins/Buildkite tooling; version 99999.0.0 is the canonical shape used to win private-registry resolution). Its package.json preinstall script runs automatically on npm install and performs installer-side credential harvest: it collects os.hostname(), username, cwd, platform, and arch; probes CI-specific environment variables (HORDE_AGENT, GITHUB_ACTIONS, JENKINS_URL, TEAMCITY_VERSION); and enumerates process.env filtering by the regex /^(AWS_|GITHUB_|GH_|NPM_|EPIC_|UE_|HORDE_|P4|CI|BUILD|TOKEN|KEY|SECRET)/i, taking up to 30 matching variables. The collected data is POSTed as JSON over plain HTTP to the bare-IP endpoint http://109.123.247.172/npm/ue_jenkins_buildkite, and an out-of-band DNS beacon is issued to
Source: ghsa-malware (55fd457fdd033f752d6550cdd66a9f0d98348f07c118af4e5f75a4eb9948b7d2)
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 (a67a3300cb2357e9661889459167d34c43be7925bd3d476d3a08588d9a907b59)
The OpenSSF Package Analysis project identified 'ue-jenkins-buildkite' @ 99999.0.0 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
References
Ready to move
Start Securing
Free, no credit card | First findings in minutes