Which versions of @ensdomains/ens-contracts are malicious?

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

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

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

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

Yes — @ensdomains/ens-contracts is associated with the GHSA-58x9-4xmp-8mg5 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/ens-contracts 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/ens-contracts (version 1.6.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ensdomains/ens-contracts across your stack and pipelines.

Malicious package

@ensdomains/ens-contractsnpm

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

MAL-2025-190931

Immediate action

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

npm uninstall @ensdomains/ens-contracts

What this malware does

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

1.6.1

Indicators of compromise (SHA-256)

2100f4fc9df15bbad549cd2656566b0f67f3275bf872479bc35f08f7fef0414e

dee805b6610ec644c5edb2b73ca1d1da2119bb3280f182e716cfdd0aa31720fb

72f6ea6e4682d9b2805bca00d852932e7f800092c11403706f58ee165e5491ce

598c4f68de12f026b60f0b86c03119e5fee43b0ed120df71cd1bf9a31d33e4f6

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

Campaign

GHSA-58x9-4xmp-8mg5

References

Credits

Amazon Inspector · finder

Detect & block this

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