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

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

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

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

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

Is @public-for-cdao/bot part of a known attack campaign?

Yes — @public-for-cdao/bot is associated with the RLMA-2026-05448, RLUA-2026-05904 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/bot across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @public-for-cdao/bot (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/botnpm

Advisory published Jul 20, 2026Updated Sep 1, 2026

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

MAL-2026-10883

Immediate action

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

npm uninstall @public-for-cdao/bot

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

43e42db1768db96008e6ee70f15d339cb328af56cab9e8f58eabbc5da72f3451

f16e0f93b876ba1f1fd1c7433d7ba4668032395de2f7e9482540b6f941b75928

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @public-for-cdao/bot (version 99.99.99).
If you installed it — respond
Remove @public-for-cdao/bot 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/bot 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/bot 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

RLMA-2026-05448RLUA-2026-05904

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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