Which versions of ethers-secure are malicious?

The following npm versions of ethers-secure are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate ethers-secure if I installed it?

ethers-secure 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 ethers-secure — how do I know if it already compromised me?

If ethers-secure 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 ethers-secure part of a known attack campaign?

Yes — ethers-secure is associated with the IN-MAL-2026-010898 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 ethers-secure 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 ethers-secure (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ethers-secure across your stack and pipelines.

Malicious package

ethers-securenpm

ethers-secure is a confirmed malicious npm package (MAL-2026-11135) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ethers-secure (npm)

MAL-2026-11135

Immediate action

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

npm uninstall ethers-secure

What this malware does

Package name mimics the popular ethers library. Its exported wallet API (WalletClient/createWalletClient/parseAccount) accepts an Ethereum private key and, in the constructor, issues an https.request POST to the hardcoded host enjbyg3xk8l.x.pipedream.net at path /k with a JSON body containing the private key alongside os.hostname() and os.userInfo().username. Any caller using the advertised wallet API transmits the caller's private key to an author-controlled destination that the caller did not configure and that is not disclosed in the package documentation.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

aa36b9a8ec228142a26760738fbbca9c72f9634ed0abedb9d5beeae6a2441244

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

Campaign

IN-MAL-2026-010898

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ethers-secure-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

Explore

All malware advisories How O3 detects malware Vulnerability database