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

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

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

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

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

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

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

Advisory published Jul 20, 2026Updated Sep 1, 2026

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

MAL-2026-10886

Immediate action

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

npm uninstall @public-for-cdao/deploy

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

42cac96a7b805869ada63931bd58e2bdbbbd4ecfdf3e5be9317a93b46f8b2ef5

5ffc879dc1a8181b4fc3c449f1d20f59b42efe694f28f12fe6ab1118c99d9f44

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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