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

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

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

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

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

Yes — @public-for-cdao/abi is associated with the IN-MAL-2026-010546, RLMA-2026-05445, RLUA-2026-05901 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/abi 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/abi (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/abi 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/abinpm

@public-for-cdao/abi is a confirmed malicious npm package (MAL-2026-10599) 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/abi (npm)

MAL-2026-10599

Immediate action

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

npm uninstall @public-for-cdao/abi

What this malware does

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

The package installs a postinstall script (recon.js) that runs automatically on npm install. The script enumerates a hardcoded list of installer environment variables (including AWS_SECRET_ACCESS_KEY, CI_JOB_TOKEN, NPM_TOKEN, MNEMONIC, private-key and database-password names), scans multiple.env file paths for lines matching KEY/SECRET/TOKEN/PASS/MNEMONIC patterns, and collects host identifiers (hostname, platform, arch, username, cwd) plus directory listings under /builds/, /home/gitlab-runner/builds/, /tmp/, and /var/lib/gitlab-runner/. The collected JSON payload is written to /tmp/.npm_recon_<ts>.json and POSTed via https.request to two attacker-controlled endpoints: webhook.site and enqoojbegdvxj.x.pipedream.net. The package name @public-for-cdao/abi with a 99.99.99 version and an index.js that returns {name:'@cdao/abi'} targets a private @cdao/abi scope via dependency confusion; a code comment labels the file 'CryptoDAO Dependency Confusion Reconnaissance Payload'.

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

102277e30b4f56dba5ebfb6a6a0ba076163907bfd28b2055b7fe6870261071f6

d8fbc16350fd94be835470e9558413038b2d7981b144015827b53bffe5270d23

8c0b5f6e74449443302d99c3238bd137f58a88cd02b44cab233b10b888186abf

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/abi (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/abi across your stack and pipelines.
If you installed it — respond
@public-for-cdao/abi 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/abi 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/abi 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/abi 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-010546RLMA-2026-05445RLUA-2026-05901

References

Credits

Amazon Inspector · finder
ReversingLabs · finder
YoSheep · finder

Detect & block this

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