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

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

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

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

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

Yes — @ensdomains/ens-validation is associated with the GHSA-7qf5-372p-99qc 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-validation 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-validation (version 0.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ensdomains/ens-validation across your stack and pipelines.

Malicious package

@ensdomains/ens-validationnpm

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

MAL-2025-190731

Immediate action

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

npm uninstall @ensdomains/ens-validation

What this malware does

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

0.1.1

Indicators of compromise (SHA-256)

888cda258fc91c14364a2fbb54c5915dce803b479ae956687755db865001fdc6

173e84cfbbc1d7f66bf31e3f547ed242f523d13cbe076c7b1c70ad771cad5b53

f525ab513d80ecfd11be91aaec93631386929e285d8611916e530dbd980c4788

06930d112812f3cf873af651de769c69e0cfe2ee41112dc7d0c1dcd3b0aede6d

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

Campaign

GHSA-7qf5-372p-99qc

References

Credits

Amazon Inspector · finder

Detect & block this

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