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, RLMA-2026-05449, RLUA-2026-05905 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.

Part of a larger attack: @public-for-cdao published 15 malicious packages. See the full campaign →

Malicious package

@public-for-cdao/commonnpm

@public-for-cdao/common is a confirmed malicious npm package (MAL-2026-10601) that steals credentials and exfiltrates sensitive data (malicious version 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

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

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

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.

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

28545511de9101d471f9f9184bd6b86c16380ab3f4740f3772e794ce270b6aa5

b0985a716da0a29b9610aff57cdfede383d868859413ad41e42cd88c94c47ef7

1cd1950c11a2826ba83e686b1c9f3de7ebbe36263ea384fc6c8af4d54c1aaf53

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-010542RLMA-2026-05449RLUA-2026-05905

References

Credits

Amazon Inspector · finder
ReversingLabs · finder
YoSheep · 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

Explore

All malware advisories How O3 detects malware Vulnerability database