NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Part of a larger attack: @public-for-cdao published 16 malicious packages. See the full campaign →
Malicious package

@public-for-cdao/providersnpm

Advisory published Updated

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

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

MAL-2026-20045
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @public-for-cdao/providers

What this malware does

Malicious package. A postinstall hook runs node recon.js, which shells out to read the last 100 lines of ~/.bash_history and ~/.zsh_history, ~/.gitconfig, ~/.npmrc and the first line of ~/.ssh/id_rsa, and sends the results to a hardcoded endpoint, https://cdao-c2.aduljune.workers.dev/c2/exfil. Observed in a sandboxed install (file reads, the shell commands and the connection to cdao-c2.aduljune.workers.dev). Same dependency-confusion credential-theft campaign as other packages in the @public-for-cdao scope already in OSV, with a different exfiltration endpoint. The package has been removed from npm.

Malicious versions

1 flagged
1.0.1

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @public-for-cdao/providers (version 1.0.1).

  2. If you installed it — respond

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

  3. Did it already run?

    If @public-for-cdao/providers was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @public-for-cdao/providers on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

  • wormsign · finder

Detect & block this

O3 blocks @public-for-cdao/providers-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

@public-for-cdao/providers (npm) malicious package — MAL-2026-20045 | O3 Security