# MAL-2026-5969: Malicious code in cryptodao-sdk (npm)


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

## What is MAL-2026-5969?

MAL-2026-5969 is a malicious package in cryptodao-sdk, published on 17 Jun 2026. 

### Official description

cryptodao-sdk@99.99.99 ships a postinstall script (recon.js) that runs automatically on `npm install` and harvests installer-side secrets. The script enumerates a hardcoded list of credential-bearing environment variables (including AWS_SECRET_ACCESS_KEY, NPM_TOKEN, CI_JOB_TOKEN, GitLab tokens, database passwords, PRIVATE_KEY, MNEMONIC, RPC URLs, Docker credentials), reads.env files from common application paths, and lists CI build directories. The collected data, along with host metadata (hostname, platform, user, cwd), is POSTed over HTTPS to two attacker-controlled endpoints — webhook.site/d6d18927-... and enqoojbegdvxj.x.pipedream.net — with TLS verification explicitly disabled (rejectUnauthorized:false). A copy is also written to /tmp/.npm_recon_<ts>.json. The package.json sets version 99.99.99 (a classic dependency-confusion override to outrank private internal packages of the same name), the description claims it is an internal CryptoDAO module, and recon.js self-identifies in a comment as a 'CryptoDAO Dependency Confusion Reconnaissance Payload'. The combination of dep-confusion namespace abuse with install-time credential exfiltration is an unambiguous supply-chain attack.

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

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

## Sources

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

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