# MAL-2026-6932: Malicious code in evm-typechain (npm)


- **Type:** Malicious package
- **Package:** `evm-typechain` (npm)
- **Published:** 7 Jul 2026
- **Also known as:** GHSA-c4gm-jp6q-h9hq

## What is MAL-2026-6932?

MAL-2026-6932 is a malicious package in evm-typechain, published on 7 Jul 2026. 

### Official description

On require, index.js issues an HTTPS GET to https://www.jsonkeeper.com/b/PC5CK, passes the returned JSON `cookie` field to `new Function('require',...)`, and invokes it with the real `require` capability. The invocation is concealed at the end of index.js behind a long run of tab whitespace on the same line as `module.exports = leanhooksPlugin;`, and the file carries a false `Mongoose LeanHooks Plugin` header that does not match the package's advertised purpose. The remote content is attacker-mutable (unpinned, no hash/signature) and executes with full module-loading capability, giving arbitrary remote code execution in any Node.js process that imports the package. The package name and description impersonate the widely used TypeChain project (`type-safe bindings for Ethereum smart contracts`), while the shipped code is an unrelated Mongoose plugin stub bolted to the remote loader; the repository URL (`drudge/evm-typeschain`) is a spelling mismatch. This is a typosquat lure fronting an import-time RCE dropper.

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-6932?

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-6932 is a malicious package: evm-typechain (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-6932/ (Markdown: https://insights.sbomify.com/MAL-2026-6932/index.md)
```

## Sources

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

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