Malicious Code Detected in buildkite-runner: A Critical Security Alert

buildkite-runner Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16330: Malicious code in buildkite-runner (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The buildkite-runner package is a tool designed for continuous integration and deployment, allowing developers to automate their build processes. It is widely used in various software projects due to its efficiency and ease of integration with popular CI/CD platforms. However, recent findings have revealed that this package contains malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability in the buildkite-runner package stems from the inclusion of malicious code that can compromise the integrity of applications utilizing this package. This malicious code can lead to unauthorized access, data breaches, and potential exploitation of the affected systems. The issue was introduced in version 0 and affects all subsequent versions, making it imperative for users to take immediate action to mitigate risks.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall buildkite-runner

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary measure, users can remove the buildkite-runner package from their project until a secure version is available. This can be done using the following command: npm uninstall buildkite-runner. Additionally, consider using alternative CI/CD tools that do not have known vulnerabilities.

Conclusion

The discovery of malicious code in the buildkite-runner package highlights the importance of vigilance in software dependencies. Users are urged to take immediate action by updating or removing the affected package to safeguard their applications. Utilizing tools like Vulert can further enhance security by providing real-time vulnerability alerts.

See every vulnerability recorded for buildkite-runner →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to systems and data, leading to security breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

As of now, a patched version is not specified. Users should monitor the package repository for updates.

Consider uninstalling the buildkite-runner package and using alternative solutions until a secure version is available.

Vulert uses the package-lock.json file to monitor and alert users in real-time for open-source vulnerabilities without requiring code access or installation.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall buildkite-runner

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback