Which versions of applogger_ruby are malicious?

The following RubyGems versions of applogger_ruby are flagged malicious: 0.5.3. Treat any of these as compromised.

How do I remediate applogger_ruby if I installed it?

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

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

Yes — applogger_ruby is associated with the RLMA-2024-05458, RLUA-2024-09977 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 applogger_ruby across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for applogger_ruby (version 0.5.3).

Malicious package

applogger_rubyRubyGems

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

Malicious code in applogger_ruby (RubyGems)

MAL-2024-6652

Immediate action

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

gem uninstall applogger_ruby

Malicious versions

1 flagged

0.5.3

Indicators of compromise (SHA-256)

40ce98b67960348f9caf50b1727dcf9ba47f3d59e7f2c70822059c7453e88ed6

2dd17ffaeccf5b55dfedfa10bfea164defb37495f5e355d4dcf2a95989754f31

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05458RLUA-2024-09977

References

blog.reversinglabs.com

Credits

ReversingLabs · finder

Detect & block this

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