# MAL-2026-4554: Malicious code in ethers-wallet-packages (npm)


- **Type:** Malicious package
- **Package:** `ethers-wallet-packages` (npm)
- **Published:** 20 May 2026
- **Also known as:** GHSA-gm49-5q33-vf6f

## What is MAL-2026-4554?

MAL-2026-4554 is a malicious package in ethers-wallet-packages, published on 20 May 2026. 

### Official description

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.

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.

## What should I do about MAL-2026-4554?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-4554 is a malicious package: ethers-wallet-packages (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-4554/ (Markdown: https://insights.sbomify.com/MAL-2026-4554/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-4554

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-4554/
Summaries are generated and may contain mistakes; the official description above is the record.