Which versions of logging_logstash are malicious?

The following RubyGems versions of logging_logstash are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate logging_logstash if I installed it?

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

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

Yes — logging_logstash is associated with the RLMA-2024-05782, RLUA-2024-10302, RLUA-2026-08512 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 logging_logstash across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for logging_logstash (version 0.1.0).

Malicious package

logging_logstashRubyGems

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

Malicious code in logging_logstash (RubyGems)

MAL-2024-6976

Immediate action

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

gem uninstall logging_logstash

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

9f396c79c79ed7f6ce1f7e839539da0211da9450e1ef93f32b0681cc1957502a

f107bf06d04a48acba79314dc3f4483c44d4f826a2a42648fb3aa8eb0ef17ff0

ae9f4910ada3e7dffbff524e20ef2079b465839ec496a4500e9d71fa033ae9a7

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05782RLUA-2024-10302RLUA-2026-08512

References

Credits

ReversingLabs · finder

Detect & block this

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