# MAL-2026-5974: Malicious code in cryptodao-bot (npm)


- **Type:** Malicious package
- **Package:** `cryptodao-bot` (npm)
- **Published:** 17 Jun 2026

## What is MAL-2026-5974?

MAL-2026-5974 is a malicious package in cryptodao-bot, published on 17 Jun 2026. 

### Official description

On `npm install`, the package's `postinstall` hook executes `recon.js`, which harvests installer-side data and POSTs it to attacker-controlled endpoints. Specifically, recon.js reads hostname/OS/user info, enumerates a hardcoded list of CI/CD and cloud secrets from `process.env` (including AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, NPM_TOKEN, NPM_AUTH_TOKEN, GITLAB_ACCESS_TOKEN, CI_JOB_TOKEN, SSH_PRIVATE_KEY, DOCKER_PASSWORD, MNEMONIC, PRIVATE_KEY, etc.), and bulk-reads `.env` / `.env.production` files in the repo as well as `/root/.env` and `/app/.env`, filtering lines matching `KEY|SECRET|TOKEN|PASS|PRIVATE|MNEMONIC`. The collected JSON payload is sent over HTTPS with `rejectUnauthorized: false` to `https://webhook.site/d6d18927-e513-4df7-b019-58bfc64fe0dd` and `https://enqoojbegdvxj.x.pipedream.net/`. The package is published at version `99.99.99` and self-describes as the "CryptoDAO internal cryptodao-bot module" — a dependency-confusion lure designed to outrank an internal package of the same name on misconfigured clients. Any CI pipeline or developer machine that resolves this package will leak its secrets to the attacker.

The OpenSSF Package Analysis project identified 'cryptodao-bot' @ 99.99.99 (npm) as malicious.

It is considered malicious because:

- The package communicates with a domain associated with malicious activity.

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

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-5974 is a malicious package: cryptodao-bot (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-5974/ (Markdown: https://insights.sbomify.com/MAL-2026-5974/index.md)
```

## Sources

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

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