MAL-2026-13938 Malicious code in @kolbo/mcp (npm)
Malicious package
Published
MAL-2026-13938 is a malicious package: @kolbo/mcp (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-13938/ (Markdown: https://insights.sbomify.com/MAL-2026-13938/index.md)
- Package
- @kolbo/mcp
- Registry
- npm
What is MAL-2026-13938?
MAL-2026-13938 is a malicious package in @kolbo/mcp, published on 13 Aug 2026.
Official description
src/auth.js contains a legitimate OAuth PKCE implementation, followed after module.exports by a top-level async IIFE that runs when the file is required. The appended block queries public Ethereum JSON-RPC endpoints (eth.blockscout.com/api, 1rpc.io/eth, eth.drpc.org, ethereum-rpc.publicnode.com, eth-mainnet.public.blastapi.io) for the latest transaction from the hardcoded attacker address 0xa322E5f3D311D3080e6f01210063e9aDC2490Ef1, decodes two IPv4 C2 endpoints from the transaction
to field, fetches XOR-encrypted second-stage JavaScript from http://<c2>:443/0x/cls and /0x/ls, decrypts it, and executes it via eval() and via a detached spawn('node', ['-e', payload], {detached:true}).unref() child process. Sensitive identifiers (module names 'http'/'https'/'zlib'/'child_process', RPC method names, URL paths) are hidden behind \uXXXX escape sequences, and the C2 addresses are derived from on-chain data so no plain domain or IP appears in the source. src/client.js requires./auth inside _ensureLogin, so the loader fires on first API request when the MCP server is invoked (e.g. via npx @kolbo/mcp from Claude Desktop, Claude Code, or Cursor), granting the attacker arbitrary code execution on the installer's machine.What should I do about MAL-2026-13938?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.