Which versions of @ensdomains/react-ens-address are malicious?

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

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

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

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

Yes — @ensdomains/react-ens-address is associated with the GHSA-vj6r-g9qw-frr9 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/react-ens-address 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/react-ens-address (version 0.0.32). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ensdomains/react-ens-address across your stack and pipelines.

Malicious package

@ensdomains/react-ens-addressnpm

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

MAL-2025-190809

Immediate action

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

npm uninstall @ensdomains/react-ens-address

What this malware does

The package @ensdomains/react-ens-address 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.0.32

Indicators of compromise (SHA-256)

cba211ae33ea36a3514f7889b5c96a143b5700d5b5b470afed1a32583deb4c99

7c136b64e27be18d7c3aeebbcd6a31479adacc70efae5bbf586009180e51098a

4a3f43ae17a1b6c5339e7188d53f6f81d9e2a4d547fac15f7ba7a588305ccd22

255582476614367d6d2d06888c95f76c9cb568cab37d60a3e86b57bdd879e99f

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

Campaign

GHSA-vj6r-g9qw-frr9

References

Credits

Amazon Inspector · finder

Detect & block this

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