Which versions of commandsy_plugin are malicious?

The following RubyGems versions of commandsy_plugin are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate commandsy_plugin if I installed it?

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

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

Yes — commandsy_plugin is associated with the RLMA-2024-05645, RLUA-2024-10164, RLUA-2026-07940 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 commandsy_plugin across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for commandsy_plugin (version 0.0.1).

Malicious package

commandsy_pluginRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in commandsy_plugin (RubyGems)

MAL-2024-6839

Immediate action

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

gem uninstall commandsy_plugin

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1a21328a16d9c61552f5ca0ecd21dc8616c5c664d378d3f0bf464284da705e1c

86e2f1d37fde4abc862494b03f9aa5a35e5448590af1ab336be6ad58681b3e35

ae7a422499cc182f1dbe60fcc7c3b8dda44529a867065ec31f705b2a0e980961

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05645RLUA-2024-10164RLUA-2026-07940

References

Credits

ReversingLabs · finder

Detect & block this

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