Which versions of rubylogger are malicious?

The following RubyGems versions of rubylogger are flagged malicious: 99.9.2, 99.9.3, 99.9.8, 99.9.9. Treat any of these as compromised.

How do I remediate rubylogger if I installed it?

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

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

Yes — rubylogger is associated with the RLMA-2026-00958, RLUA-2026-09089 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 rubylogger across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for rubylogger (4 malicious versions).

Malicious package

rubyloggerRubyGems

Advisory published Mar 18, 2026Updated Sep 24, 2026

rubylogger is a confirmed malicious RubyGems package (MAL-2026-1922) that executes malicious code on install (malicious versions 99.9.2, 99.9.3, 99.9.8…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rubylogger (RubyGems)

MAL-2026-1922

Immediate action

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

gem uninstall rubylogger

Malicious versions

4 flagged

99.9.299.9.399.9.899.9.9

Indicators of compromise (SHA-256)

a94effc7d600b08174e8eee1e642777d604d1f7097605f9c62cfdc9db4ea4537

5d78f7d7814d838405dd7edfc62dfb63272f96798f0b932b9a7c785797a19e11

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-00958RLUA-2026-09089

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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