mnemonic-to-key (npm) · Malicious Code
Affects mnemonic-to-keySource GCVE Database
Malicious package : remove mnemonic-to-key and rotate any secrets on hosts that installed it.
Data as of 5 Aug 2026, 23:00 UTC
Malicious package
Published to npm · OSV MAL-2026-13349
What to do
Remove mnemonic-to-key from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmmnemonic-to-key | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The npm package 'mnemonic-to-key' version 1.2.0 contains malicious code that exfiltrates environment variables and system information to a Telegram bot on first import. It acts as a typosquat for the legitimate 'bip39' package, targeting cryptocurrency developers by capturing sensitive data such as API tokens and cloud credentials from process environments. The package sends this data encoded via HTTPS GET requests and suppresses repeated transmissions using a flag file.