Which versions of log4r_logstash are malicious?

The following RubyGems versions of log4r_logstash are flagged malicious: 0.1.1. Treat any of these as compromised.

How do I remediate log4r_logstash if I installed it?

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

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

Yes — log4r_logstash is associated with the RLMA-2024-05781, RLUA-2024-10301, RLUA-2026-08511 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 log4r_logstash across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for log4r_logstash (version 0.1.1).

Malicious package

log4r_logstashRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in log4r_logstash (RubyGems)

MAL-2024-6975

Immediate action

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

gem uninstall log4r_logstash

Malicious versions

1 flagged

0.1.1

Indicators of compromise (SHA-256)

406702cbab8c1aabddd8a4a84064556874dc88ebe489e9f770d710b9af7a2735

6d119847532c9cfe7aa92ca78002d374c1022ae8ba5ac6377776a4ee261cb148

a9aa25145ed9d33bd61f70f3943f04f2f0cacf1b540b6c3237a3c46f3f038e91

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05781RLUA-2024-10301RLUA-2026-08511

References

Credits

ReversingLabs · finder

Detect & block this

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