Which versions of @google_cloud/projectify are malicious?

The following npm versions of @google_cloud/projectify are flagged malicious: 20.1.1. Treat any of these as compromised.

How do I remediate @google_cloud/projectify if I installed it?

Remove @google_cloud/projectify 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 @google_cloud/projectify — how do I know if it already compromised me?

If @google_cloud/projectify 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.

Is @google_cloud/projectify part of a known attack campaign?

Yes — @google_cloud/projectify is associated with the GHSA-2888-9m8h-fcw3, RLMA-2025-04837, RLUA-2026-01014 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 @google_cloud/projectify across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @google_cloud/projectify (version 20.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @google_cloud/projectify across your stack and pipelines.

Malicious package

@google_cloud/projectifynpm

@google_cloud/projectify is a confirmed malicious npm package (MAL-2025-47030) that executes malicious code on install (malicious version 20.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @google_cloud/projectify (npm)

MAL-2025-47030

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @google_cloud/projectify

What this malware does

The package @google_cloud/projectify 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

1 flagged

20.1.1

Indicators of compromise (SHA-256)

348dd9384a1e11bd9559bcdb3d4e2ef98ad16da2967df02ad4b6764b8d9ef2af

64a89161a268f242f966f4729bf6cec970f053ceca20eda1706ef8e780a89498

43545bcab9d16cffbf3d309a64f1db81ef8c1fc2c42eba2c2a47a90b337cde45

a93b4ee8c56d188d9a54e3faec19c47e1e1a15486ae57ca72421ebb89d3ef949

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @google_cloud/projectify (version 20.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @google_cloud/projectify across your stack and pipelines.
If you installed it — respond
Remove @google_cloud/projectify 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 @google_cloud/projectify 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.
How O3 protects you
O3 blocks @google_cloud/projectify 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. @google_cloud/projectify on npm has been identified as a malicious package (version 20.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-2888-9m8h-fcw3RLMA-2025-04837RLUA-2026-01014

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @google_cloud/projectify-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