NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

ethereum-ensnpm

Advisory published Updated

ethereum-ens is a confirmed malicious npm package (MAL-2025-190696) that steals credentials and exfiltrates sensitive data (malicious version 0.8.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ethereum-ens (npm)

MAL-2025-190696
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall ethereum-ens

What this malware does

The package ethereum-ens 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.8.1

Indicators of compromise (SHA-256)

08b4862efdbd7fabbe626b338824bea3a86cdb7a190c176ab6ddc665f9ecf080
874848c97832c07d7093bf8c59c73549a0f9b8c2ecffeab4d33a5c3fbcfb6a4a
6df52b6cf02ac0bf2ac794cb0e0dac4e690d9c1e7e674a5fac35e937cdd46b85

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for ethereum-ens (version 0.8.1).

  2. If you installed it — respond

    ethereum-ens 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.

  3. Did it already run?

    If ethereum-ens was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. ethereum-ens on npm has been identified as a malicious package (version 0.8.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-whx3-vxm3-8xjh

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks ethereum-ens-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

ethereum-ens (npm) malicious package — MAL-2025-190696 | O3 Security