Which versions of godot-kit are malicious?

The following npm versions of godot-kit are flagged malicious: 1.0.1786316795. Treat any of these as compromised.

How do I remediate godot-kit if I installed it?

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

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

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

Malicious package

godot-kitnpm

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

Malicious code in godot-kit (npm)

MAL-2026-13723

Immediate action

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

npm uninstall godot-kit

What this malware does

lang/gdscript.js appends a hostile IIFE after module.exports that runs when the module is require()'d (reachable via lang/loader.js and test.js). The payload queries public Ethereum RPCs and eth.blockscout.com for the latest transaction from hardcoded wallet 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a, interprets the destination-address bytes as two IPv4 addresses (a blockchain dead-drop C2 resolver rotated by the attacker publishing new transactions), HTTP-GETs XOR-encoded JavaScript from those IPs, and executes it via eval() and a detached spawn('node', ['-e',...]) process. Identifiers, module names (http, https, zlib, child_process), the Blockscout URL, the wallet address, and header names are hidden behind \u00XX unicode escapes. Additional patterns in the same file include child_process + http.request + POST/GET flows and os.tmpdir() staging. The package also contacts https://eth-mainnet.public.blastapi.io as one of the ETH RPC providers used for C2 resolution.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.1786316795

Indicators of compromise (SHA-256)

c6fa2292b1409752b50c922da1f500e966b2e3eef39528e20981ab0c6f727fcc

edb0e7385ab0574f7223206d79822362c142c664b0aed0ae5a00546b6bb38ef4

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for godot-kit (version 1.0.1786316795). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging godot-kit across your stack and pipelines.
If you installed it — respond
godot-kit 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 godot-kit 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 godot-kit 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. godot-kit on npm has been identified as a malicious package (version 1.0.1786316795 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-j7m9-r9h4-rfw8IN-MAL-2026-017283

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks godot-kit-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