Malicious code in @public-for-cdao/api (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-10600
PublishedThe @public-for-cdao/api package is part of a dependency-confusion credential theft campaign. Its package.json declares a postinstall hook that runs node recon.js automatically during npm installation. The bundled recon.js is identical across six packages in the @public-for-cdao scope and has SHA-256 3dd1f7827fe311d17f442e0af0fab46f3f1a938bb3409838536795fb1aa0f740. The script collects CI tokens, GitLab access tokens, SSH and deployment keys, AWS credentials, database and Redis passwords, private keys, cryptocurrency mnemonics and seed phrases, Docker and npm credentials, and Slack and Discord tokens from environment variables. It also searches common project, application, root, and CI-runner locations for .env files and extracts lines containing KEY, SECRET, TOKEN, PASS, PRIVATE, or MNEMONIC. The package name, version, hostname, and collected secrets are POSTed to a fixed webhook.site endpoint and a Pipedream endpoint with TLS certificate verification disabled. --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (4d844c4af5615aa5e7eb8470e79d2e95b841e91a8a23df81bafdb56f656b0111) @public-for-cdao/[email protected] is a high-version public squat of a presumed private @cdao/api scope (index.js exports name '@cdao/api'; package description 'CryptoDAO api module - internal use'). package.json declares a postinstall script that runs recon.js on `npm install`. recon.js enumerates a curated list of ~30 CI/CD, cloud, wallet, and registry secret environment variables (including AWS_SECRET_ACCESS_KEY, CI_JOB_TOKEN, NPM_TOKEN, GITLAB_ACCESS_TOKEN, DOCKER_PASSWORD, PRIVATE_KEY, MNEMONIC), scans multiple.env file paths for lines matching KEY/SECRET/TOKEN/PASS/PRIVATE/MNEMONIC, collects host identifiers (hostname, OS, arch, username, cwd) and directory listings of /builds/, /home/gitlab-runner/builds/, /tmp/, and /var/lib/gitlab-runner/, and HTTPS-POSTs the aggregated payload with rejectUnauthorized:false to two hardcoded exfiltration endpoints: https://webhook.site/d6d18927-e513-4df7-b019-58bfc64fe0dd and https://enqoojbegdvxj.x.pipedream.net. The recon.js header comment self-labels the file as 'CryptoDAO Dependency Confusion Reconnaissance Payload'.
- Source published
- 17 Jun 2026 03:50:13 UTC
- Source modified
- 1 Sep 2026 11:30:52 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.