Which versions of cache-stats are malicious?

The following RubyGems versions of cache-stats are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate cache-stats if I installed it?

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

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

Yes — cache-stats is associated with the RLMA-2024-05605, RLUA-2024-10124 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 cache-stats across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for cache-stats (version 0.0.1).

Malicious package

cache-statsRubyGems

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

Malicious code in cache-stats (RubyGems)

MAL-2024-6799

Immediate action

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

gem uninstall cache-stats

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

114645183d6bad26dfb21d42dd74fa5de21ba7a1555f59fe6843097bd810cc72

1eede04bc58dbeae7141009b56fba0aae37a5a6589716f006bb699596fe836dd

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05605RLUA-2024-10124

References

blog.reversinglabs.com

Credits

ReversingLabs · finder

Detect & block this

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