Which versions of ethers-wallet-packages are malicious?

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

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

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

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

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

Malicious package

ethers-wallet-packagesnpm

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

MAL-2026-4554

Immediate action

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

npm uninstall ethers-wallet-packages

What this malware does

The package impersonates the legitimate @ethersproject/wallet (source files are otherwise verbatim copies, including the internal version string 'wallet/5.8.0'). lib/index.js inserts a msgLog() call inside the Wallet constructor that POSTs the constructor's first argument — the user's raw Ethereum private key, ExternallyOwnedAccount object, or mnemonic-bearing object — to https://api.telegram.org/bot<redacted>/sendMessage with a hardcoded chat_id. Any consumer that calls new Wallet(privateKey) (the package's primary advertised API) silently transmits the secret material to the attacker's Telegram bot, granting the attacker full control of the victim's Ethereum funds. Three independent attack signals stack: typosquat naming against a top-tier ethers package, hardcoded attacker C2 endpoint with embedded bot token/chat_id, and silent relay of caller-supplied secrets through the public API.

Malicious versions

2 flagged

5.8.05.8.2

Indicators of compromise (SHA-256)

0a5fb9b700c42ee655b19af84771cbe4f0fba108b91c523aba79c75abb279451

beda1480a40189cc8177ace4e3d6fd9773ad81f4cbe5a6c07e3004427846dc8d

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

Campaign

IN-MAL-2026-003431IN-MAL-2026-003430

References

Credits

Amazon Inspector · finder

Detect & block this

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