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

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

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

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

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

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

Malicious package

@public-for-cdao/commonnpm

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

MAL-2026-10601

Immediate action

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

npm uninstall @public-for-cdao/common

What this malware does

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.

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

28545511de9101d471f9f9184bd6b86c16380ab3f4740f3772e794ce270b6aa5

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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