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

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

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

Remove @public-for-cdao/hooks from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Can O3 Security detect @public-for-cdao/hooks in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking @public-for-cdao/hooks and packages like it before any post-install script runs.

Malicious package

@public-for-cdao/hooksnpm

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

MAL-2026-5971

Immediate action

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

npm uninstall @public-for-cdao/hooks

What this malware does

The OpenSSF Package Analysis project identified '@public-for-cdao/hooks' @ 99.99.99 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

8611956b7ad849ba2a98285fa33897da931deb28e74f30bc8a6299d567852c51

Frequently asked questions

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

Credits

OpenSSF: Package Analysis · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection