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 activity or persistence.

I already installed @public-for-cdao/hooks — how do I know if it already compromised me?

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

How do I find @public-for-cdao/hooks across my projects, lockfiles, and CI pipelines?

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

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

Malicious package

@public-for-cdao/hooksnpm

Advisory published Jun 17, 2026Updated Jun 17, 2026

@public-for-cdao/hooks is a confirmed malicious npm package (MAL-2026-5971) that executes malicious code on install (malicious version 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

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

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

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @public-for-cdao/hooks (version 99.99.99).
If you installed it — respond
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 activity or persistence.
Did it already run?
If @public-for-cdao/hooks 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/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

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database