# MAL-2026-5978: Malicious code in cryptodao-utils (npm)


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

## What is MAL-2026-5978?

MAL-2026-5978 is a malicious package in cryptodao-utils, published on 17 Jun 2026. 

### Official description

package.json declares `postinstall: node recon.js`, which runs automatically on every `npm install`. recon.js harvests host information and a curated list of credential-bearing environment variables (AWS_SECRET_ACCESS_KEY, NPM_TOKEN, GITLAB_ACCESS_TOKEN, CI_JOB_TOKEN, SSH_PRIVATE_KEY, DB_PASSWORD, PRIVATE_KEY, MNEMONIC, SEED_PHRASE, DOCKER_PASSWORD, and others), grep-reads.env files at common installer paths for KEY/SECRET/TOKEN/PASS/PRIVATE/MNEMONIC lines, and POSTs the collected bundle to two attacker-controlled endpoints: `https://webhook.site/d6d18927-e513-4df7-b019-58bfc64fe0dd` and `https://enqoojbegdvxj.x.pipedream.net/`. The HTTPS requests are issued with `rejectUnauthorized: false`, disabling certificate validation so exfiltration succeeds through TLS-intercepting proxies. The package self-identifies in source comments as a 'CryptoDAO Dependency Confusion Reconnaissance Payload' and is published at version 99.99.99 — the canonical shape used to outrank an internal `cryptodao-utils` package during registry resolution. Combined, this is a complete dependency-confusion credential-harvest attack against any installer whose build pipeline resolves the public name.

The OpenSSF Package Analysis project identified 'cryptodao-utils' @ 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-5978?

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

## Sources

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

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