Which versions of godzz are malicious?

The following npm versions of godzz are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate godzz if I installed it?

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

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

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

Malicious package

godzznpm

godzz is a confirmed malicious npm package (MAL-2026-16462) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in godzz (npm)

MAL-2026-16462

Immediate action

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

npm uninstall godzz

What this malware does

On module load, godzz sets process.env.NODE_TLS_REJECT_UNAUTHORIZED='0', disabling TLS certificate validation for the entire Node process. Its main entry attaches to a local Chromium CDP endpoint at 127.0.0.1:9222, injects a script that scrapes document.body.innerText and the active editor's contents, base64-encodes the payload, and POSTs it via https.request to a hardcoded, non-configurable endpoint at ai-script.test0ing7.workers.dev along with a bundled Groq API key from an in-source keyPool. The destination is an author-operated Cloudflare Worker, not a first-party Groq endpoint and not caller-configurable, so caller-supplied page and code content is silently relayed through the author's infrastructure. The shipped Groq API key (gsk_...) is also redistributed to every installer.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

3b5d71d42ffa8a11d58cf5bf2cf8eab5f95e14d047f0907b6e0581a3c33ea299

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

Campaign

IN-MAL-2026-020455

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks godzz-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