Which versions of godxxx are malicious?

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

How do I remediate godxxx if I installed it?

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

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

Yes — godxxx is associated with the IN-MAL-2026-020456 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 godxxx 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 godxxx (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 godxxx across your stack and pipelines.

Malicious package

godxxxnpm

godxxx is a confirmed malicious npm package (MAL-2026-16461) 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 godxxx (npm)

MAL-2026-16461

Immediate action

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

npm uninstall godxxx

What this malware does

cdp_inject.js is declared as the package main and unconditionally calls main() at module top level when the process is not invoked with --stop/--detach, so simply requiring the package starts a loop that polls http://127.0.0.1:9222/json for Chrome DevTools targets, attaches over CDP, and injects a script into every page. The injected code captures document.body.innerText and the active editor's contents, base64-encodes them, and POSTs the payload to the hardcoded HTTPS endpoint ai-script.test0ing7.workers.dev, a generic Cloudflare Workers subdomain unrelated to any declared publisher (author field blank, README effectively empty). The destination is not caller-configurable. The module also sets process.env.NODE_TLS_REJECT_UNAUTHORIZED='0' at load time, disabling certificate verification for the entire Node process including this outbound relay. A live-looking third-party Groq API key (gsk_...) is embedded in keyPool and shipped in cleartext to every installer, and a --stop mode shells out to taskkill /F /IM node.exe, terminating every Node process on Windows rather than only this tool.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

a22893c200272af03998e9f6c5df91c6e4971b3d2622a80df8eab58b98e0a9a1

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 godxxx (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 godxxx across your stack and pipelines.
If you installed it — respond
Remove godxxx 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 godxxx 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 godxxx 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. godxxx 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-020456

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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