Which versions of cryptodao-deploy are malicious?

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

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

Remove cryptodao-deploy from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is cryptodao-deploy part of a known attack campaign?

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

Can O3 Security detect cryptodao-deploy in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking cryptodao-deploy and packages like it before any post-install script runs.

Malicious package

cryptodao-deploynpm

Malicious code in cryptodao-deploy (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5968

Immediate action

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

npm uninstall cryptodao-deploy

What this malware does

package.json declares postinstall: node recon.js, which fires automatically on npm install. recon.js enumerates installer-side secrets — AWS_SECRET_ACCESS_KEY, NPM_TOKEN, GITLAB_ACCESS_TOKEN, SSH_PRIVATE_KEY, DB_PASSWORD, MNEMONIC and similar credential-shaped environment variables — reads .env files at multiple paths, and lists CI runner directories such as /builds/ and /home/gitlab-runner/. It also collects host/identity reconnaissance (hostname, platform, user, cwd, CI_PROJECT_PATH, CI_JOB_ID, CI_REGISTRY_USER/PASSWORD). The collected data is JSON-serialized and POSTed via https.request with rejectUnauthorized:false to webhook.site/d6d18927-e513-4df7-b019-58bfc64fe0dd and enqoojbegdvxj.x.pipedream.net. The package is named cryptodao-deploy and published at version 99.99.99 with an in-source comment 'CryptoDAO Dependency Confusion Reconnaissance Payload', indicating intent to override an internal private package via dependency-confusion resolution and run the exfil payload inside the victim's CI.

The OpenSSF Package Analysis project identified 'cryptodao-deploy' @ 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)

2611f17b04a754eafe632f845f449c6bd036c048ac8b1c31295491524ccaecaa

5323b2fc30e7603b402729f45345a9c3eb4af8361acaca5d035cc51f9e660cea

Frequently asked questions

No. cryptodao-deploy 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-006866

References

npmjs.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection