Which versions of evm-checkcode-cli are malicious?

The following npm versions of evm-checkcode-cli are flagged malicious: 1.0.12, 1.0.13, 1.0.14, 1.0.15. Treat any of these as compromised.

How do I remediate evm-checkcode-cli if I installed it?

evm-checkcode-cli 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 evm-checkcode-cli — how do I know if it already compromised me?

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

Yes — evm-checkcode-cli is associated with the GHSA-mc99-3j32-7fmh 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-checkcode-cli 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-checkcode-cli (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging evm-checkcode-cli across your stack and pipelines.

Malicious package

evm-checkcode-clinpm

Malicious code in evm-checkcode-cli (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190841

Immediate action

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

npm uninstall evm-checkcode-cli

What this malware does

The package evm-checkcode-cli was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

4 flagged

1.0.121.0.131.0.141.0.15

Indicators of compromise (SHA-256)

039b61897974a873cedd4880336a6ea7c2e7d7bc060f1a9281ca38c9f1615ef7

67c49d35b6096e7c647d830c11a75a90f1bd3b90677f1c72d1bdefcd87b134e8

816f6cfcf8fe0b847c3bbc89549a27d1a5eed29c2e7aae734bf2f94daf45c911

17a73a885439e5b529da4f92151ea02b07d3a811b3de756ae002cb3004499145

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 evm-checkcode-cli (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging evm-checkcode-cli across your stack and pipelines.
If you installed it — respond
evm-checkcode-cli 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 evm-checkcode-cli 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-checkcode-cli 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-checkcode-cli on npm has been identified as a malicious package (versions 1.0.12, 1.0.13, 1.0.14, 1.0.15 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-mc99-3j32-7fmh

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks evm-checkcode-cli-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