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

cmp-api-stubnpm

cmp-api-stub is a confirmed malicious npm package (MAL-2026-6662) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cmp-api-stub (npm)

MAL-2026-6662
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall cmp-api-stub

What this malware does

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.

Malicious versions

1 flagged
99.9.1

Indicators of compromise (SHA-256)

64a5a4ba35daee6a6a7e344f853e6ab0fc54d4d39f3434bdd3cbc7e7f56aa766
5ab0506535af939fc3f22ddeacce490af33c4d402365d8d90631c956c1e8b2bb
f8bdef5a7061d0e95e7d8e360c1fa5b61c09896a56d7fec7395973768f1b1008

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 cmp-api-stub (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cmp-api-stub across your stack and pipelines.

  2. If you installed it — respond

    Remove cmp-api-stub 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 cmp-api-stub 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 cmp-api-stub 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. cmp-api-stub on npm has been identified as a malicious package (version 99.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-q9xg-g7r9-mqrxRLMA-2026-05026RLUA-2026-05518

References

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks cmp-api-stub-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.

Explore

cmp-api-stub (npm) malicious package — MAL-2026-6662 | O3 Security