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

@girirajravichandran/corp-build-utils-pocnpm

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

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

What this malware does

The package @girirajravichandran/corp-build-utils-poc was found to contain malicious code.

Malicious versions

2 flagged
99.9.2999.9.31

Indicators of compromise (SHA-256)

c3fd3c6573713ac03147f039d38fa6d43614996bc6f3ad44007c31bf5b41ab53
82e79f342b1cd33520c8987b0307cb211e4b04694caef9c967725778e1802e94
f2ca2d526cc484891da34c40490d46c6419c48971ba4ea0930f114f4a03962b1

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

  2. If you installed it — respond

    Remove @girirajravichandran/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 @girirajravichandran/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 @girirajravichandran/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. @girirajravichandran/corp-build-utils-poc on npm has been identified as a malicious package (versions 99.9.29, 99.9.31 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01695RLUA-2026-01856

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks @girirajravichandran/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.

@girirajravichandran/corp-build-utils-poc (npm) malicious package — MAL-2026-2331 | O3 Security