# MAL-2026-11529: Malicious code in @zzzgenesis00/crypto-config (npm)


- **Type:** Malicious package
- **Package:** `@zzzgenesis00/crypto-config` (npm)
- **Published:** 4 Aug 2026

## What is MAL-2026-11529?

MAL-2026-11529 is a malicious package in @zzzgenesis00/crypto-config, published on 4 Aug 2026. 

### Official description

postinstall.js runs automatically on `npm install` and enumerates installer-owned secret material: SSH private keys under ~/.ssh, ~/.npmrc, ~/.gitconfig, Chrome/Firefox profile cookie/login/key databases, cryptocurrency wallet directories (metamask, exodus, electrum, etc.), and a curated list of sensitive environment variables including NPM_TOKEN, AWS keys, GitHub tokens, ETHEREUM_PRIVATE_KEY, and MNEMONIC. It also invokes `npm whoami` and `git config user.email` to bind the exfil to a specific identity. The collected profile is sent via HTTPS GET to api.telegram.org using a hardcoded bot token and chat_id, and via HTTPS POST to a hardcoded serveousercontent.com tunnel endpoint at /collect; neither destination is caller-configurable. Delivery is jittered via setTimeout(1500 + Math.random()*2000) and identifiers throughout the script are mangled (_vaa, _zmj, _rlb, _cp, _ht, _tk, _ch, _co, _ex). The package name, author field (`lorenwest`, the maintainer of the legitimate `config` package), and homepage impersonate a benign configuration library, and index.js transparently proxies to the real `config` package when present as a cover for the install-time payload.

## What should I do about MAL-2026-11529?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-11529 is a malicious package: @zzzgenesis00/crypto-config (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-11529/ (Markdown: https://insights.sbomify.com/MAL-2026-11529/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-11529

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-11529/
Summaries are generated and may contain mistakes; the official description above is the record.