Which versions of evm-typechain are malicious?

The following npm versions of evm-typechain are flagged malicious: 0.5.4. Treat any of these as compromised.

How do I remediate evm-typechain if I installed it?

evm-typechain is a typosquat — you almost certainly intended a legitimately-named package. Remove evm-typechain, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed evm-typechain — how do I know if it already compromised me?

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

Yes — evm-typechain is associated with the GHSA-c4gm-jp6q-h9hq, IN-MAL-2026-009287 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 evm-typechain 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 evm-typechain (version 0.5.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging evm-typechain across your stack and pipelines.

Malicious package

evm-typechainnpm

evm-typechain is a confirmed malicious npm package (MAL-2026-6932) that typosquats a legitimate package to trick installs (malicious version 0.5.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in evm-typechain (npm)

MAL-2026-6932

Immediate action

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

npm uninstall evm-typechain

What this malware does

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.

Malicious versions

1 flagged

0.5.4

Indicators of compromise (SHA-256)

7f309e50be1b9923d440673fba72e6c345b370828f8d8a0e313afb6d6d2e96f0

0a78b4d04410e295cbe340c95e6800a0777717d46ce136f0c30b5593d1bd9738

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for evm-typechain (version 0.5.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging evm-typechain across your stack and pipelines.
If you installed it — respond
evm-typechain is a typosquat — you almost certainly intended a legitimately-named package. Remove evm-typechain, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If evm-typechain 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 evm-typechain 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. evm-typechain on npm has been identified as a malicious package (version 0.5.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-c4gm-jp6q-h9hqIN-MAL-2026-009287

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks evm-typechain-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