Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

buildkite-test-collector-cypress-examplenpm

Malicious code in buildkite-test-collector-cypress-example (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2731
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall buildkite-test-collector-cypress-example

What this malware does

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

Malicious versions

1 flagged
99.99.9

Indicators of compromise (SHA-256)

a036bcf5b60d33fa8baaf4818884530e2a6cf3ce9afd8463c208f9f0adae0f25
1c10094969be88bd9f1aa924abf89c5dc58dd70e107adf3c95a3f58c0ba86518

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for buildkite-test-collector-cypress-example (version 99.99.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging buildkite-test-collector-cypress-example across your stack and pipelines.

  2. If you installed it — respond

    Remove buildkite-test-collector-cypress-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.

  3. Did it already run?

    If buildkite-test-collector-cypress-example 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.

  4. How O3 protects you

    O3 blocks buildkite-test-collector-cypress-example 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

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

Campaign

RLMA-2026-01897

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks buildkite-test-collector-cypress-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.

buildkite-test-collector-cypress-example (npm) malicious package — MAL-2026-2731 | O3 Security