Which versions of fastgrc-openclaw are malicious?

The following npm versions of fastgrc-openclaw are flagged malicious: 1.0.33. Treat any of these as compromised.

How do I remediate fastgrc-openclaw if I installed it?

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

If fastgrc-openclaw 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 fastgrc-openclaw part of a known attack campaign?

Yes — fastgrc-openclaw is associated with the IN-MAL-2026-003692 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 fastgrc-openclaw 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 fastgrc-openclaw (version 1.0.33). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fastgrc-openclaw across your stack and pipelines.

Malicious package

fastgrc-openclawnpm

Malicious code in fastgrc-openclaw (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4558

Immediate action

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

npm uninstall fastgrc-openclaw

What this malware does

The package is an AI agent policy-check plugin. When a consumer does not configure their own API key, resolveApiKey() returns a hardcoded BUNDLED_API_KEY (fgrc_k1_8b8cd6c4df4685cd1bae986bb992c7a9f188fc6e in dist/index.js line 46, also present in dist/plugin.js and dist/bin.js). The plugin's before_tool_call hook then POSTs every tool name and full argument payload to https://app.fastgrc.ai/api/v1/policy-router/evaluate authenticated with that key. The README and an in-code warning state that tool calls will 'proceed unchecked' if no key is set, but the code actually relays them to the author's FastGRC tenant. As a result, any agent's tool-call data — which can include caller-supplied prompts, file paths, command arguments, and other contextual data — leaves the installer's machine to a third-party endpoint the installer never opted into. The destination matches the package author (app.fastgrc.ai), but the silent-relay behavior contradicts documented behavior and ships caller data off-host without consent.

Malicious versions

1 flagged

1.0.33

Indicators of compromise (SHA-256)

158457237168ef50e3a6c4cd33f51e23f6aec642593745a3d11b9b4870ef36ce

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

Campaign

IN-MAL-2026-003692

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks fastgrc-openclaw-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