# MAL-2026-13723: Malicious code in godot-kit (npm)


- **Type:** Malicious package
- **Package:** `godot-kit` (npm)
- **Published:** 10 Aug 2026
- **Also known as:** GHSA-j7m9-r9h4-rfw8

## What is MAL-2026-13723?

MAL-2026-13723 is a malicious package in godot-kit, published on 10 Aug 2026. 

### Official description

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.

## What should I do about MAL-2026-13723?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-13723 is a malicious package: godot-kit (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-13723/ (Markdown: https://insights.sbomify.com/MAL-2026-13723/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-13723

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-13723/
Summaries are generated and may contain mistakes; the official description above is the record.