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

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

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

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

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

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

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

Advisory published Jul 20, 2026Updated Sep 1, 2026

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

MAL-2026-10885

Immediate action

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

npm uninstall @public-for-cdao/core

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

feef2ee3b81dac72b0cbc72d0a797ab88f248358fe399d2da425bdd54bfe74ed

6700a0c4fb46323bdeeec26fa26e2b8485850e833969a2c02e9ae121f41562ad

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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