Malicious code in ethers-wallet-package (npm)
MAL-2026-4553 · GHSA-7pvf-g7jg-rxpj
Published · Modified
Dependency scanning
Check whether ethers-wallet-package is in your codebase
Corgea flags malicious and compromised dependencies with reachability analysis, so you fix the packages that actually run in your application instead of working through the whole lockfile.
Description
__
Source: amazon-inspector (c6dae6dc459fa2ef437e532af4b27b6c50360a40cdb9d91563d25a48bae88cec)
Package name impersonates the official @ethersproject/wallet, and package.json spoofs the ethers.js maintainer identity (author 'Richard Moore me@ricmoo.com'). 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/botnew 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.
Source: ghsa-malware (220ce4e0be76da392304c8cfc16d134919d9a35c6925ea0a6df8c9e562ed0e62)
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.
References
Ready to move
Start Securing
Free, no credit card | First findings in minutes