ue-jenkins-buildkitenpm
ue-jenkins-buildkite is a confirmed malicious npm package (MAL-2026-6731) 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 ue-jenkins-buildkite (npm)
What this malware does
[email protected] 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 <host>-<user>.ue_jenkins_buildkite.npm.epic-dc.oast.fun. The regex is a credential-shaped bulk scraper (AWS keys, GitHub tokens, npm publish tokens, generic TOKEN/KEY/SECRET variables) unrelated to any legitimate build-tool license check.
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 'ue-jenkins-buildkite' @ 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 ue-jenkins-buildkite (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 ue-jenkins-buildkite across your stack and pipelines.
If you installed it — respond
ue-jenkins-buildkite 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 ue-jenkins-buildkite 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 ue-jenkins-buildkite 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 ue-jenkins-buildkite-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.