Which versions of @public-for-cdao/types are malicious?

The following npm versions of @public-for-cdao/types are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate @public-for-cdao/types if I installed it?

@public-for-cdao/types 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 @public-for-cdao/types — how do I know if it already compromised me?

If @public-for-cdao/types 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 @public-for-cdao/types part of a known attack campaign?

Yes — @public-for-cdao/types is associated with the IN-MAL-2026-010545 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 @public-for-cdao/types 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 @public-for-cdao/types (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 @public-for-cdao/types across your stack and pipelines.

Malicious package

@public-for-cdao/typesnpm

Malicious code in @public-for-cdao/types (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10604

Immediate action

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

npm uninstall @public-for-cdao/types

What this malware does

The package's postinstall script (scripts.postinstall = 'node recon.js') runs automatically on npm install and performs an installer-side credential and reconnaissance harvest. recon.js collects os.hostname(), platform, arch, user, and cwd; enumerates approximately 40 CI/CD, cloud, and wallet-related environment variables including AWS_SECRET_ACCESS_KEY, NPM_TOKEN, GitLab tokens, database and Redis passwords, PRIVATE_KEY, MNEMONIC, and SEED_PHRASE; reads.env files at common paths via fs.readFileSync; and lists directories under /builds, /home/gitlab-runner/builds/, /tmp/, and /var/lib/gitlab-runner/. The collected JSON payload is POSTed via https.request to webhook.site (path /d6d18927-e513-4df7-b019-58bfc64fe0dd) and to enqoojbegdvxj.x.pipedream.net. The package name (@public-for-cdao/types), the pinned version 99.99.99, index.js exporting { name: '@cdao/types', version: '99.99.99' } as a stub, and the in-file comment 'CryptoDAO Dependency Confusion Reconnaissance Payload' identify this as a targeted dependency-confusion attack against an internal '@cdao/types' package.

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

5b1047a119646917a21b103985170a9e993dee0d95a7b6f1f261ddea944b3bf5

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 @public-for-cdao/types (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 @public-for-cdao/types across your stack and pipelines.
If you installed it — respond
@public-for-cdao/types 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 @public-for-cdao/types 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 @public-for-cdao/types 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. @public-for-cdao/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-010545

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @public-for-cdao/types-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