Which versions of claide_plugins are malicious?

The following RubyGems versions of claide_plugins are flagged malicious: 0.9.2. Treat any of these as compromised.

How do I remediate claide_plugins if I installed it?

Remove claide_plugins 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 claide_plugins — how do I know if it already compromised me?

If claide_plugins 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 claide_plugins part of a known attack campaign?

Yes — claide_plugins is associated with the RLMA-2024-05638, RLUA-2024-10157, RLUA-2026-07932 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 claide_plugins across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for claide_plugins (version 0.9.2).

Malicious package

claide_pluginsRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

claide_plugins is a confirmed malicious RubyGems package (MAL-2024-6832) that executes malicious code on install (malicious version 0.9.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in claide_plugins (RubyGems)

MAL-2024-6832

Immediate action

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

gem uninstall claide_plugins

Malicious versions

1 flagged

0.9.2

Indicators of compromise (SHA-256)

78bfc33fcf331d57ffe0e1febe4f805c2cb877ec5207e3871177a0eaab86f5fc

365ee84f83aacac74190eb469e2ffc9977caf643b07ae8409c1b99c2b9933a66

174cb081d723e4ea4bcf8f02ee9288fb69d5175788cc64302f4b61919619e86c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for claide_plugins (version 0.9.2).
If you installed it — respond
Remove claide_plugins 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 claide_plugins 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. claide_plugins on RubyGems has been identified as a malicious package (version 0.9.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-05638RLUA-2024-10157RLUA-2026-07932

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks claide_plugins-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