Which versions of @ensdomains/content-hash are malicious?

The following npm versions of @ensdomains/content-hash are flagged malicious: 3.0.1. Treat any of these as compromised.

How do I remediate @ensdomains/content-hash if I installed it?

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

If @ensdomains/content-hash 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/content-hash part of a known attack campaign?

Yes — @ensdomains/content-hash is associated with the GHSA-29f6-8xrp-f68w 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/content-hash 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/content-hash (version 3.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ensdomains/content-hash across your stack and pipelines.

Malicious package

@ensdomains/content-hashnpm

Malicious code in @ensdomains/content-hash (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190666

Immediate action

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

npm uninstall @ensdomains/content-hash

What this malware does

The package @ensdomains/content-hash 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

3.0.1

Indicators of compromise (SHA-256)

acc5b8835460a7af0effab91e3fecfb09a2fc8818ec068d25b35f39655e89004

39aeb9f2a2d9a8ee1c57695456c8af6657d069eaee694ef7f8c128bb292bfabd

99f5d25e4be7650c1614dd38c4df501ebef4411f00ad5037c0362064eebae6a9

3ef9bab3a9af409b905e8f9f1bdd06d3214e7ca350481aec7b9f0cc3147772c6

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

Campaign

GHSA-29f6-8xrp-f68w

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @ensdomains/content-hash-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