Which versions of @ensdomains/eth-ens-namehash are malicious?

The following npm versions of @ensdomains/eth-ens-namehash are flagged malicious: 2.0.16. Treat any of these as compromised.

How do I remediate @ensdomains/eth-ens-namehash if I installed it?

@ensdomains/eth-ens-namehash 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 @ensdomains/eth-ens-namehash — how do I know if it already compromised me?

If @ensdomains/eth-ens-namehash 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 @ensdomains/eth-ens-namehash part of a known attack campaign?

Yes — @ensdomains/eth-ens-namehash is associated with the GHSA-p274-4jv4-6mpx 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 @ensdomains/eth-ens-namehash 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 @ensdomains/eth-ens-namehash (version 2.0.16). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ensdomains/eth-ens-namehash across your stack and pipelines.

Malicious package

@ensdomains/eth-ens-namehashnpm

Malicious code in @ensdomains/eth-ens-namehash (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190667

Immediate action

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

npm uninstall @ensdomains/eth-ens-namehash

What this malware does

The package @ensdomains/eth-ens-namehash 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

1 flagged

2.0.16

Indicators of compromise (SHA-256)

eef4ea757c2666bc6358373523661681558d83debcabe61911516c223021aab1

c0009bf3870d33e9e174ce53fe0a281b43402e1f8b78f62e6cd296ad8f082588

17d6c7fae98b969dfb273cbbdc59f67992bc10d3135ebee91b297154d5cc4ec5

5885432add03db52674c50bde5883262dc4cbebb20d6d335111711f3ac54003c

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 @ensdomains/eth-ens-namehash (version 2.0.16). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ensdomains/eth-ens-namehash across your stack and pipelines.
If you installed it — respond
@ensdomains/eth-ens-namehash 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 @ensdomains/eth-ens-namehash 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 @ensdomains/eth-ens-namehash 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. @ensdomains/eth-ens-namehash on npm has been identified as a malicious package (version 2.0.16 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-p274-4jv4-6mpx

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @ensdomains/eth-ens-namehash-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