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

corp-build-utils-pocnpm

Malicious code in corp-build-utils-poc (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1220
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall corp-build-utils-poc

What this malware does

The package corp-build-utils-poc 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

18 flagged
99.9.999.9.1099.9.1199.9.1299.9.1399.9.1499.9.1699.9.1999.9.2099.9.2199.9.2299.9.2399.9.2499.9.2599.9.2699.9.2799.9.2899.9.29

Indicators of compromise (SHA-256)

b9c08039f74952076819a6954c4eda81ce12c5e76315b203f9d833f708e2482d
862b2e0a8f0028f96ee10ab1a7c8ea0fc397169634a9473a09865a173c483c92
abd99af46830e52c28a477cf439ac3ab5ee8c250235bc809b08a7842e1dc6ac6

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 corp-build-utils-poc (18 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging corp-build-utils-poc across your stack and pipelines.

  2. If you installed it — respond

    Remove corp-build-utils-poc 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 corp-build-utils-poc 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 corp-build-utils-poc 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. corp-build-utils-poc on npm has been identified as a malicious package (versions 99.9.9, 99.9.10, 99.9.11, 99.9.12, 99.9.13, 99.9.14, 99.9.16, 99.9.19, and 10 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-788f-4r73-p46jRLMA-2026-01732

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks corp-build-utils-poc-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.

corp-build-utils-poc (npm) malicious package — MAL-2026-1220 | O3 Security