Which versions of @girirajravichandran/corp-build-utils-poc are malicious?

The following npm versions of @girirajravichandran/corp-build-utils-poc are flagged malicious: 99.9.29, 99.9.31. Treat any of these as compromised.

How do I remediate @girirajravichandran/corp-build-utils-poc if I installed it?

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.

I already installed @girirajravichandran/corp-build-utils-poc — how do I know if it already compromised me?

If @girirajravichandran/corp-build-utils-poc 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.

Is @girirajravichandran/corp-build-utils-poc part of a known attack campaign?

Yes — @girirajravichandran/corp-build-utils-poc is associated with the RLMA-2026-01695, RLUA-2026-01856 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @girirajravichandran/corp-build-utils-poc across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @girirajravichandran/corp-build-utils-poc (2 malicious versions).

Malicious package

@girirajravichandran/corp-build-utils-pocnpm

Advisory published Mar 24, 2026Updated Apr 16, 2026

@girirajravichandran/corp-build-utils-poc is a confirmed malicious npm package (MAL-2026-2331) that executes malicious code on install (malicious versions 99.9.29, 99.9.31). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @girirajravichandran/corp-build-utils-poc (npm)

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

Find it
Search your lockfiles and build artifacts for @girirajravichandran/corp-build-utils-poc (2 malicious versions).
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.
Did it already run?
If @girirajravichandran/corp-build-utils-poc 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. @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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database