VDB
KO

MAL-2026-12056

Malicious code in @zzzgenesis00/mnemonic-to-key (npm)

Details

--- _-= Per source details. Do not edit below this line.=-_

## Source: amazon-inspector (c3af286f89deaee9dcce3d85f9bd53bc2b03e63dccf0073c74988b3f3a3763e8) 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.

Are you affected?

Enter the version of the package you're using.

Affected packages

npm / @zzzgenesis00/mnemonic-to-key

No fixed version published yet for @zzzgenesis00/mnemonic-to-key (npm). Pin to a known-safe version or switch to an alternative.

References