Which versions of rails-structured-logging are malicious?

The following RubyGems versions of rails-structured-logging are flagged malicious: 90002.0. Treat any of these as compromised.

How do I remediate rails-structured-logging if I installed it?

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

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

Yes — rails-structured-logging is associated with the RLMA-2025-06625, RLUA-2026-09026 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 rails-structured-logging across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for rails-structured-logging (version 90002.0).

Malicious package

rails-structured-loggingRubyGems

Advisory published Dec 23, 2025Updated Sep 24, 2026

rails-structured-logging is a confirmed malicious RubyGems package (MAL-2025-192915) that executes malicious code on install (malicious version 90002.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rails-structured-logging (RubyGems)

MAL-2025-192915

Immediate action

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

gem uninstall rails-structured-logging

Malicious versions

1 flagged

90002.0

Indicators of compromise (SHA-256)

f655ca1326c2851bf180104a7948ca52111ff910dd4d9cdab41ad067dac77161

a32b7a284cb2c73487978adab6898081aaa8a5f9fdb5dd7ca911eeb5a92c2080

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06625RLUA-2026-09026

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks rails-structured-logging-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