Which versions of buildkite-test-collector-jest-example are malicious?

The following npm versions of buildkite-test-collector-jest-example are flagged malicious: 99.99.9, 99.99.10. Treat any of these as compromised.

How do I remediate buildkite-test-collector-jest-example if I installed it?

Remove buildkite-test-collector-jest-example from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed buildkite-test-collector-jest-example — how do I know if it already compromised me?

If buildkite-test-collector-jest-example was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is buildkite-test-collector-jest-example part of a known attack campaign?

Yes — buildkite-test-collector-jest-example is associated with the RLMA-2026-01899 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find buildkite-test-collector-jest-example across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for buildkite-test-collector-jest-example (2 malicious versions).

Malicious package

buildkite-test-collector-jest-examplenpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

buildkite-test-collector-jest-example is a confirmed malicious npm package (MAL-2026-2733) that executes malicious code on install (malicious versions 99.99.9, 99.99.10). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in buildkite-test-collector-jest-example (npm)

MAL-2026-2733

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall buildkite-test-collector-jest-example

What this malware does

The package buildkite-test-collector-jest-example was found to contain malicious code.

Malicious versions

2 flagged

99.99.999.99.10

Indicators of compromise (SHA-256)

a4d8a83757f178218251d1766f26369bc207eca04a48d4decd6d3deaa218ca7d

b6fa2618170566c342534726ad9c855cf62ad98ee9b6e815e5324c5bc4779da2

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for buildkite-test-collector-jest-example (2 malicious versions).
If you installed it — respond
Remove buildkite-test-collector-jest-example from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If buildkite-test-collector-jest-example was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. buildkite-test-collector-jest-example on npm has been identified as a malicious package (versions 99.99.9, 99.99.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01899

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks buildkite-test-collector-jest-example-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database