NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Part of a larger attack: @wethenorth12 published 23 malicious packages. See the full campaign →
Malicious package

@wethenorth12/mnemonic-to-keynpm

Advisory published Updated

@wethenorth12/mnemonic-to-key is a confirmed malicious npm package (MAL-2026-12097) 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 @wethenorth12/mnemonic-to-key (npm)

MAL-2026-12097
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @wethenorth12/mnemonic-to-key

What this malware does

Package advertises itself as a drop-in replacement for bip39 and exposes stub wallet functions (createWallet, generateMnemonic) to attract wallet-handling projects. On module load, index.js reads the full process.env dictionary along with hostname, username, home directory, platform, and cwd, JSON-encodes and base64-encodes the payload, and transmits it as a URL query parameter to a hardcoded Telegram Bot API sendMessage endpoint (bot 7231970337, chat 8969499041). A temporary flag file is written to suppress repeated sends. Environment variables in developer and CI environments routinely contain cloud credentials, npm/GitHub tokens, and database secrets, so the require-time beacon is a direct credential-theft channel controlled by the package author.

Malicious versions

1 flagged
1.2.0

Indicators of compromise (SHA-256)

c373b3f6b1c60d079fb7c63d13a51f7e42ee41feeff2c04c5ab925ad5dad41fb

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for @wethenorth12/mnemonic-to-key (version 1.2.0).

  2. If you installed it — respond

    @wethenorth12/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.

  3. Did it already run?

    If @wethenorth12/mnemonic-to-key was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @wethenorth12/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-013434

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @wethenorth12/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
@wethenorth12/mnemonic-to-key (npm) malicious package — MAL-2026-12097 | O3 Security