Which versions of mnemonic-to-key are malicious?

The following npm versions of mnemonic-to-key are flagged malicious: 1.2.0. Treat any of these as compromised.

How do I remediate mnemonic-to-key if I installed it?

mnemonic-to-key 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 mnemonic-to-key — how do I know if it already compromised me?

If mnemonic-to-key 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 mnemonic-to-key part of a known attack campaign?

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

Malicious package

mnemonic-to-keynpm

mnemonic-to-key is a confirmed malicious npm package (MAL-2026-13349) that steals credentials and exfiltrates sensitive data (malicious version 1.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mnemonic-to-key (npm)

MAL-2026-13349

Immediate action

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

npm uninstall mnemonic-to-key

What this malware does

On require(), index.js serializes the full process.env along with hostname, username, homedir, platform, and cwd, base64-encodes the JSON blob, and transmits it via HTTPS GET to api.telegram.org using a hardcoded bot token (7231970337) and chat_id (8969499041). A flag file under the OS tmpdir suppresses repeat sends. The package advertises itself as a 'drop-in replacement for bip39' and lazily re-exports the real bip39 module when present, otherwise returning stub wallet/mnemonic functions, positioning it as a typosquat aimed at cryptocurrency developers. process.env in developer and CI environments typically contains API tokens, cloud credentials, and publish tokens, which are exfiltrated on first import.

Malicious versions

1 flagged

1.2.0

Indicators of compromise (SHA-256)

c8871a9cd738ee7dbe2245e741d52afb659069bc6fcc7d5aa6cfb87bfad9dbcd

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

Campaign

IN-MAL-2026-015782

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks mnemonic-to-key-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

Explore

All malware advisories How O3 detects malware Vulnerability database