Which versions of @zzzgenesis00/mnemonic-to-key are malicious?

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

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

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

I already installed @zzzgenesis00/mnemonic-to-key — how do I know if it already compromised me?

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

Yes — @zzzgenesis00/mnemonic-to-key is associated with the IN-MAL-2026-011965 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 @zzzgenesis00/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 @zzzgenesis00/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 @zzzgenesis00/mnemonic-to-key across your stack and pipelines.

Malicious package

@zzzgenesis00/mnemonic-to-keynpm

@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

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @zzzgenesis00/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 @zzzgenesis00/mnemonic-to-key across your stack and pipelines.
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.
Did it already run?
If @zzzgenesis00/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 @zzzgenesis00/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. @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

npmjs.com

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