NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

cp_ammnpm

Advisory published Updated

cp_amm is a confirmed malicious npm package (MAL-2026-74) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cp_amm (npm)

MAL-2026-74
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall cp_amm

What this malware does

The package cp_amm was found to contain malicious code.

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

c2bf6dfc9b717408c1e17976ef3ecb5193dd73340f2d3a60f85d114b24c81c4e
6e71dacd7a89bbff73298cd870eab40b71d5fdf8a2ffbec74c772cbc4e6f1026

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for cp_amm (all published versions).

  2. If you installed it — respond

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

Campaign

GHSA-qjp3-7854-4xfc

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks cp_amm-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

cp_amm (npm) malicious package — MAL-2026-74 | O3 Security