MAL-2026-10601 Malicious code in @public-for-cdao/common (npm)

Malicious package Published
Package
@public-for-cdao/common
Registry
npm

What is MAL-2026-10601?

MAL-2026-10601 is a malicious package in @public-for-cdao/common, published on 17 Jun 2026.

Official description

The @public-for-cdao/common 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.

Package declares a postinstall hook that runs recon.js on npm install. recon.js reads a broad list of secret-bearing environment variables (AWS_SECRET_ACCESS_KEY, NPM_TOKEN, SSH_PRIVATE_KEY, MNEMONIC, GitLab and CI_* tokens, DB/Redis passwords) and scans common.env file paths including /root/.env, /app/.env, and /home/gitlab-runner/.env for KEY/SECRET/TOKEN/PASS/PRIVATE/MNEMONIC matches. The harvested payload plus host identifiers is POSTed to two hardcoded non-first-party endpoints, webhook.site/d6d18927-e513-4df7-b019-58bfc64fe0dd and enqoojbegdvxj.x.pipedream.net, over HTTPS with certificate verification disabled (rejectUnauthorized:false). The package is published at version 99.99.99 under the public scope @public-for-cdao while index.js identifies itself as @cdao/common, and a source comment self-labels it a 'CryptoDAO Dependency Confusion Reconnaissance Payload' — the shape of a dependency-confusion attack against CI/CD builds that misroute an internal @cdao scope to the public registry.

What should I do about MAL-2026-10601?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

Sources

Also known as GHSA-rhm5-mc66-328f.

Is MAL-2026-10601 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free