ethereum-sign-utilsnpm
ethereum-sign-utils is a confirmed malicious npm package (MAL-2026-12110) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in ethereum-sign-utils (npm)
What this malware does
On npm install, the package's postinstall script (node postinstall.js, declared in package.json scripts.postinstall) reads installer-side secret files including.env variants, ~/.npmrc, ~/.aws/credentials, ~/.aws/config, ~/.ssh/id_rsa/id_ed25519/id_ecdsa, Solana and Ethereum keystores, and ~/.gitconfig. It also enumerates hidden directories under $HOME and reads any file under 50KB whose name matches wallet|key|secret|seed|mnemonic|keystore|private or has.json/.pem/.key extensions. Collected contents are POSTed as JSON to the hardcoded endpoint https://enxhcjpo5ev.x.pipedream.net/c. The package's main index.js is empty, so the package provides no legitimate functionality — its sole effect on install is credential and wallet-key exfiltration. The package name mimics utilities in the Ethereum tooling ecosystem as a lure.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ethereum-sign-utils (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ethereum-sign-utils across your stack and pipelines.
If you installed it — respond
ethereum-sign-utils 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 ethereum-sign-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.
How O3 protects you
O3 blocks ethereum-sign-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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks ethereum-sign-utils-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.