@public-for-cdao/types
This report shows the evidence for @public-for-cdao/types@99.99.99, the only known version.
This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.
OpenSSF/OSV Malicious Advisory
imported 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-10604 confirms this npm version as malicious.
Advisory
MAL-2026-10604
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @public-for-cdao/types (npm)
Details
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.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to @public-for-cdao/types@99.99.99.
The versions list below shows the verdict for each recorded version.
- Avoid installing @public-for-cdao/types@99.99.99. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.