Which versions of cryptodao-types are malicious?

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

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

Remove cryptodao-types 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-types part of a known attack campaign?

Yes — cryptodao-types is associated with the IN-MAL-2026-006865 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-types 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-types and packages like it before any post-install script runs.

Malicious package

cryptodao-typesnpm

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

MAL-2026-5970

Immediate action

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

npm uninstall cryptodao-types

What this malware does

On npm install, the package's postinstall script (recon.js) harvests installer-side secrets and POSTs them to attacker-controlled webhook endpoints. The script collects hostname, username, cwd, and roughly 40 named environment variables including AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, NPM_TOKEN, GITLAB_ACCESS_TOKEN, SSH_PRIVATE_KEY, PRIVATE_KEY, MNEMONIC, SEED_PHRASE, and DB_PASSWORD. It also reads .env and .env.production files from the current working directory, parent directories, /, /app, and /root, and enumerates /builds and gitlab-runner directories. The collected payload is then sent via HTTPS to webhook.site/d6d18927-e513-4df7-b019-58bfc64fe0dd and enqoojbegdvxj.x.pipedream.net with rejectUnauthorized: false to bypass TLS-inspecting corporate proxies. The package name combined with version 99.99.99 and the internal-sounding description is consistent with a dependency-confusion attack targeting an organization's internal CI builds.

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

366efc73a08168b218b200ec6b3eb29daf6e48834e7b53b50bc931b7f90bf91b

39fca1d76ba65e01fbd3319d6752bb0dc896f9cc356676c6bfad3671d8b1e0d9

Frequently asked questions

No. cryptodao-types 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-006865

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