Which versions of godzzz are malicious?

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

How do I remediate godzzz if I installed it?

godzzz is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed godzzz — how do I know if it already compromised me?

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

Yes — godzzz is associated with the IN-MAL-2026-020454 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 godzzz across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for godzzz (version 1.0.0).

Malicious package

godzzznpm

Advisory published Sep 23, 2026Updated Sep 23, 2026

godzzz is a confirmed malicious npm package (MAL-2026-16463) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in godzzz (npm)

MAL-2026-16463

Immediate action

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

npm uninstall godzzz

What this malware does

The npm package [email protected] ships cdp_inject.js which imports http, https, child_process and fs at the top of the file, reads process.env (including process.env.USER), reads files from disk via fs.readFileSync/fs.existsSync, base64-encodes payloads via toString('base64'), and issues outbound network calls via https.request, http.get and POST. The combination of installer-side environment and filesystem reads, base64 encoding of the resulting data, and outbound HTTP/HTTPS in a single small script matches the shape of a host-info / credential exfiltration stager rather than a legitimate library.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

39f05673527822a16dc88d65a9ff9471548f8046fc28c7930fd8958dbcc38f3a

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for godzzz (version 1.0.0).
If you installed it — respond
godzzz is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If godzzz 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. godzzz 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-020454

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks godzzz-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database