Which versions of rack_envinspector are malicious?

The following RubyGems versions of rack_envinspector are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate rack_envinspector if I installed it?

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

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

Yes — rack_envinspector is associated with the RLMA-2024-05812, RLUA-2024-10333, RLUA-2026-09024 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 rack_envinspector across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for rack_envinspector (version 0.1).

Malicious package

rack_envinspectorRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in rack_envinspector (RubyGems)

MAL-2024-7007

Immediate action

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

gem uninstall rack_envinspector

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

9ecfdd41ced16a2024b19a680f99e14fc38211b13f95e6be44c3d5da87fec7c4

1ef9508b74027d8139c1801adddb25cd0f05b9a446978de1eb7d6469d0df2ed8

b9042c4333f59f2b72f5b84285eb0b22b9742717e349d001ce68461f963ba43a

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05812RLUA-2024-10333RLUA-2026-09024

References

Credits

ReversingLabs · finder

Detect & block this

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