Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

eth-node-utilsnpm

eth-node-utils is a confirmed malicious npm package (MAL-2025-47179) that executes malicious code on install (malicious version 8.9.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in eth-node-utils (npm)

MAL-2025-47179
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall eth-node-utils

What this malware does

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.

Malicious versions

1 flagged
8.9.8

Indicators of compromise (SHA-256)

43e3bae1d6be9bca527622368d2a291d97b40692ce8996525eefb78917c7e0de
ffb64d3c98ec1e60a26c28df8a148a181ae4e506527655f363aa42f9894c1584
05b9031e3275422400c6be22715a1715df88dd2b710244edffb90a24a55b8645
4fcf2a627e82b869db40d65777c7aa17505a176b074a76a97c33c03a7dc8dc7d
2efcb3b2da7e9bee67f44bd3fec5f59984802bac0eb0b60d08ae52e65f82de8b

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for eth-node-utils (version 8.9.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eth-node-utils across your stack and pipelines.

  2. If you installed it — respond

    Remove eth-node-utils from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If eth-node-utils 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.

  4. How O3 protects you

    O3 blocks eth-node-utils 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. eth-node-utils on npm has been identified as a malicious package (version 8.9.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-9646-j2rv-m33jRLMA-2025-05000RLUA-2026-01299

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks eth-node-utils-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

eth-node-utils (npm) malicious package — MAL-2025-47179 | O3 Security