Which versions of gcp-api-enabler are malicious?

The following npm versions of gcp-api-enabler are flagged malicious: 99.8.1. Treat any of these as compromised.

How do I remediate gcp-api-enabler if I installed it?

Remove gcp-api-enabler 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 gcp-api-enabler — how do I know if it already compromised me?

If gcp-api-enabler 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 gcp-api-enabler part of a known attack campaign?

Yes — gcp-api-enabler is associated with the GHSA-r3rp-65c5-5cjh, RLMA-2026-05099 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 gcp-api-enabler 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 gcp-api-enabler (version 99.8.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gcp-api-enabler across your stack and pipelines.

Malicious package

gcp-api-enablernpm

gcp-api-enabler is a confirmed malicious npm package (MAL-2026-5071) that executes malicious code on install (malicious version 99.8.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in gcp-api-enabler (npm)

MAL-2026-5071

Immediate action

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

npm uninstall gcp-api-enabler

What this malware does

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

99.8.1

Indicators of compromise (SHA-256)

2a14212abcc7c3f9f662ffcc18752c5fa10f94d07ef3b7c820637eea7d02c3ab

fa6904edadfe84e5fd08eef7007c37053039db78dc2695e3cd81b631ec5dfd6e

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 gcp-api-enabler (version 99.8.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gcp-api-enabler across your stack and pipelines.
If you installed it — respond
Remove gcp-api-enabler 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 gcp-api-enabler 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 gcp-api-enabler 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. gcp-api-enabler on npm has been identified as a malicious package (version 99.8.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-r3rp-65c5-5cjhRLMA-2026-05099

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks gcp-api-enabler-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