Malicious code in @public-for-cdao/config (npm)
The @public-for-cdao/config 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.
Source: amazon-inspector
The package ships a postinstall script (recon.js) that runs at npm install time. It collects host identifiers (hostname, platform, arch, username, cwd), enumerates roughly 30 sensitive environment variables (including AWS_SECRET_ACCESS_KEY, NPM_TOKEN, GITLAB_ACCESS_TOKEN, SSH_PRIVATE_KEY, MNEMONIC, DB_PASSWORD), reads.env files from paths such as.env, /app/.env, /root/.env, and greps for lines matching KEY/SECRET/TOKEN/PASS/PRIVATE/MNEMONIC. It also enumerates CI build directories under /builds/, /home/gitlab-runner/builds/, and /var/lib/gitlab-runner/. The collected data is serialized as JSON and HTTP POSTed via https.request to two attacker-controlled collectors: webhook.site/d6d18927-e513-4df7-b019-58bfc64fe0dd and enqoojbegdvxj.x.pipedream.net. The package name and 99.99.99 version are consistent with a dependency-confusion lure targeting an internal @public-for-cdao/config scope.
