Which versions of etherscancontracthandler are malicious?

The following npm versions of etherscancontracthandler are flagged malicious: 1.0.0, 2.0.0, 3.0.0, 3.0.1, 4.0.0. Treat any of these as compromised.

How do I remediate etherscancontracthandler if I installed it?

Remove etherscancontracthandler from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed etherscancontracthandler — how do I know if it already compromised me?

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

Yes — etherscancontracthandler is associated with the GHSA-q924-4w4w-22h7, RLMA-2024-10565, RLUA-2025-06351 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 etherscancontracthandler 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 etherscancontracthandler (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging etherscancontracthandler across your stack and pipelines.

Malicious package

etherscancontracthandlernpm

etherscancontracthandler is a confirmed malicious npm package (MAL-2024-10974) that executes malicious code on install (malicious versions 1.0.0, 2.0.0, 3.0.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in etherscancontracthandler (npm)

MAL-2024-10974

Immediate action

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

npm uninstall etherscancontracthandler

What this malware does

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

5 flagged

1.0.02.0.03.0.03.0.14.0.0

Indicators of compromise (SHA-256)

c90be2cf4c6909deb4fdb88dadf2956097e88cf4bc34dbaedb4b2a34ce849b62

3530a559c52720e82ea9eb5d5dd02070b17931e3883c370c0f3bd8f75e4cc9a1

050e68e6966e94d19728454c42603ff40b9ed1e5dc587089244d90d3cf9f6ab0

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for etherscancontracthandler (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging etherscancontracthandler across your stack and pipelines.
If you installed it — respond
Remove etherscancontracthandler from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If etherscancontracthandler 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 etherscancontracthandler 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. etherscancontracthandler on npm has been identified as a malicious package (versions 1.0.0, 2.0.0, 3.0.0, 3.0.1, 4.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-q924-4w4w-22h7RLMA-2024-10565RLUA-2025-06351

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks etherscancontracthandler-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