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

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

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

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

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

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

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

Advisory published Jul 20, 2026Updated Sep 1, 2026

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

MAL-2026-10884

Immediate action

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

npm uninstall @public-for-cdao/contracts

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

ca7ebfcd4df10688b3527e1452c20ed1dbbc1036c0349715b4effc8c0a583423

8c1c747cb53aff7d873c832e67616a75697ffef758761c6e1d87ebf84b40eb6c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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