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

@zzzgenesis00/mnemonic-to-keynpm

Advisory published Updated

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

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

What this malware does

On npm install, postinstall.js executes and enumerates installer-side secrets: files under ~/.ssh (non-.pub private keys), ~/.npmrc, ~/.gitconfig, Chrome/Chromium/Firefox profile stores (Cookies, Login Data, key4.db), and cryptocurrency wallet directories (.bitcoin,.ethereum,.solana,.metamask,.exodus,.electrum, and similar). It also runs npm whoami and git config user.email and reads a list of credential-shaped environment variables including NPM_TOKEN, NODE_AUTH_TOKEN, GITHUB_TOKEN, AWS keys, MNEMONIC, SEED_PHRASE, ETHEREUM_PRIVATE_KEY, and WALLET_PRIVATE_KEY. The collected data is sent via HTTPS GET to api.telegram.org using a hardcoded bot token and chat_id, with a backup POST to a hardcoded subdomain of serveousercontent.com at path /collect. The postinstall file is disguised with a module.exports = require('./index.js') passthrough and a header comment describing it as environment verification, and exfiltration is delayed with a randomized 1.5–3.5s timer to run after install output completes. Behavior is unrelated to the package's advertised mnemonic-to-key purpose.

Malicious versions

1 flagged
1.2.0

Indicators of compromise (SHA-256)

c3af286f89deaee9dcce3d85f9bd53bc2b03e63dccf0073c74988b3f3a3763e8

Detection & response playbook

Credential / info stealer

  1. Find it

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

  2. If you installed it — respond

    @zzzgenesis00/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 @zzzgenesis00/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. @zzzgenesis00/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-011965

References

Credits

  • Amazon Inspector · finder

Detect & block this

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