Which versions of active-redis_stats are malicious?

The following RubyGems versions of active-redis_stats are flagged malicious: 0.1.3. Treat any of these as compromised.

How do I remediate active-redis_stats if I installed it?

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

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

Yes — active-redis_stats is associated with the RLMA-2024-05241, RLUA-2024-09760 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 active-redis_stats across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for active-redis_stats (version 0.1.3).

Malicious package

active-redis_statsRubyGems

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

Malicious code in active-redis_stats (RubyGems)

MAL-2024-6434

Immediate action

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

gem uninstall active-redis_stats

Malicious versions

1 flagged

0.1.3

Indicators of compromise (SHA-256)

d2c92feb7673f9dbba27eea7959706adf1e3b73091ac31156c2308e9d6214e06

2c16e9313c9f8ca30791c86b83b1d32b41e06f389cc1c62723e9a24d20130d18

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05241RLUA-2024-09760

References

blog.reversinglabs.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks active-redis_stats-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