Which versions of cryptodao-config are malicious?

The following npm versions of cryptodao-config are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate cryptodao-config if I installed it?

cryptodao-config is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed cryptodao-config — how do I know if it already compromised me?

If cryptodao-config was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is cryptodao-config part of a known attack campaign?

Yes — cryptodao-config is associated with the IN-MAL-2026-006861 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find cryptodao-config across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cryptodao-config (version 99.99.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cryptodao-config across your stack and pipelines.

Malicious package

cryptodao-confignpm

cryptodao-config is a confirmed malicious npm package (MAL-2026-5967) that steals credentials and exfiltrates sensitive data (malicious version 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cryptodao-config (npm)

MAL-2026-5967

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall cryptodao-config

What this malware does

On npm install, the postinstall hook runs node recon.js, which harvests installer-side secrets and POSTs them over HTTPS (with TLS certificate verification disabled) to two attacker-controlled collectors: webhook.site/d6d18927-e513-4df7-b019-58bfc64fe0dd and enqoojbegdvxj.x.pipedream.net. The payload (recon.js) reads a curated list of high-value environment variables — including AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, CI_JOB_TOKEN, CI_REGISTRY_PASSWORD, GITLAB_ACCESS_TOKEN, SSH_PRIVATE_KEY, NPM_TOKEN, MNEMONIC, PRIVATE_KEY, DB_PASSWORD — reads multiple .env files (./.env, /app/.env, /home/gitlab-runner/.env, /root/.env) and filters lines matching /KEY|SECRET|TOKEN|PASS|PRIVATE|MNEMONIC/i, enumerates GitLab runner build directories (/builds, /home/gitlab-runner/builds/), and ships the resulting JSON to the two endpoints. The package is published at version 99.99.99 — the canonical dependency-confusion override version — and a comment in recon.js explicitly self-identifies as a 'CryptoDAO Dependency Confusion Reconnaissance Payload', confirming intent to be auto-installed by victim pipelines that maintain an internal cryptodao-config package.

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

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

c9afe812a548e5d3b8158d3e359c37ec874e86c003476c8dc7b9de732113ca86

2b5f3b7ec6eecce3d891664f33660a1c612cdd3c6ac99ba52633ef77a2df543c

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cryptodao-config (version 99.99.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cryptodao-config across your stack and pipelines.
If you installed it — respond
cryptodao-config is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If cryptodao-config was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks cryptodao-config before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. cryptodao-config on npm has been identified as a malicious package (version 99.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006861

References

npmjs.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks cryptodao-config-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database