Which versions of cryptodao-core are malicious?

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

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

cryptodao-core 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-core — how do I know if it already compromised me?

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

Yes — cryptodao-core is associated with the IN-MAL-2026-006864 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-core 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-core (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-core across your stack and pipelines.

Malicious package

cryptodao-corenpm

cryptodao-core is a confirmed malicious npm package (MAL-2026-5976) 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-core (npm)

MAL-2026-5976

Immediate action

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

npm uninstall cryptodao-core

What this malware does

package.json declares a postinstall hook that runs recon.js on every npm install. recon.js harvests installer-side secrets — AWS_SECRET_ACCESS_KEY, SSH_PRIVATE_KEY, NPM_TOKEN, GITLAB_ACCESS_TOKEN, DB_PASSWORD, MNEMONIC and similar — reads.env files from multiple paths, enumerates CI runner directories (/builds/, /home/gitlab-runner/), and collects host fingerprint data (hostname, platform, user, cwd). The bundle is POSTed over HTTPS with TLS verification disabled (rejectUnauthorized:false) to two anonymous request-capture endpoints: webhook.site/d6d18927-e513-4df7-b019-58bfc64fe0dd and enqoojbegdvxj.x.pipedream.net. A copy is also dropped to /tmp/.npm_recon_<ts>.json. The package name 'cryptodao-core' combined with version 99.99.99 and the in-source comment 'CryptoDAO Dependency Confusion Reconnaissance Payload' is the canonical dependency-confusion attack shape — published at an absurd version to outrank an internal package of the same name on resolvers that mix public and private registries. Any CI runner or developer machine that installs this version will leak its environment secrets to attacker-controlled endpoints.

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

44bcbcde72a12ed60b3d16200226faa40f1e7e66c6ac36776710f2a0a3fec9a7

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-core (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-core across your stack and pipelines.
If you installed it — respond
cryptodao-core 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-core 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-core 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-core 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-006864

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks cryptodao-core-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