What does the ethers-wallet-package malware do?

Package name impersonates the official @ethersproject/wallet, and package.json spoofs the ethers.js maintainer identity (author 'Richard Moore '). The compiled lib/index.js wraps the Wallet constructor with an obfuscated VM-based interpreter whose base64-encoded op-array contains the plaintext target URL https://api.telegram.org/bot /sendMessage and chat_id 7959381237. On every `new Wallet(privateKey)` call, the constructor POSTs the private key as JSON to that Telegram bot, giving the attacker full control over the victim's Ethereum funds. The Wallet class is the package's only advertised API, so any caller that imports the package and constructs a wallet leaks the k

Which versions of ethers-wallet-package are malicious?

The following npm versions of ethers-wallet-package are flagged malicious: 5.8.0. Treat any of these as compromised.

How do I remediate ethers-wallet-package if I installed it?

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

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

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

Malicious package

ethers-wallet-packagenpm

Malicious code in ethers-wallet-package (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4553

Immediate action

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

npm uninstall ethers-wallet-package

What this malware does

Package name impersonates the official @ethersproject/wallet, and package.json spoofs the ethers.js maintainer identity (author 'Richard Moore [email protected]'). The compiled lib/index.js wraps the Wallet constructor with an obfuscated VM-based interpreter whose base64-encoded op-array contains the plaintext target URL https://api.telegram.org/bot<redacted>/sendMessage and chat_id 7959381237. On every new Wallet(privateKey) call, the constructor POSTs the private key as JSON to that Telegram bot, giving the attacker full control over the victim's Ethereum funds. The Wallet class is the package's only advertised API, so any caller that imports the package and constructs a wallet leaks the key on first use.

Malicious versions

1 flagged

5.8.0

Indicators of compromise (SHA-256)

c6dae6dc459fa2ef437e532af4b27b6c50360a40cdb9d91563d25a48bae88cec

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

Campaign

IN-MAL-2026-003584

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ethers-wallet-package-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