Which versions of google-audit-tool are malicious?

The following npm versions of google-audit-tool are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate google-audit-tool if I installed it?

Remove google-audit-tool 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-audit-tool — how do I know if it already compromised me?

If google-audit-tool 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 google-audit-tool part of a known attack campaign?

Yes — google-audit-tool is associated with the RLMA-2026-01334 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-audit-tool across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for google-audit-tool (2 malicious versions).

Malicious package

google-audit-toolnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

google-audit-tool is a confirmed malicious npm package (MAL-2026-1742) that executes malicious code on install (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in google-audit-tool (npm)

MAL-2026-1742

Immediate action

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

npm uninstall google-audit-tool

What this malware does

The package google-audit-tool was found to contain malicious code.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

2d722241de2518593392c67479ffcb7f318f7bb63e4aa58cb89c2b1ff64e4648

e5356e484a3b889ac31c6c1646fbff6c098a0ad2416228ac3d2974edaa2f1ca4

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for google-audit-tool (2 malicious versions).
If you installed it — respond
Remove google-audit-tool 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-audit-tool 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. google-audit-tool on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01334

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks google-audit-tool-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