Which versions of get-stats are malicious?

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

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

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

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

Yes — get-stats is associated with the RLMA-2024-05737, RLUA-2024-10256, RLUA-2026-08147 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 get-stats across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for get-stats (version 0.3).

Malicious package

get-statsRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in get-stats (RubyGems)

MAL-2024-6931

Immediate action

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

gem uninstall get-stats

Malicious versions

1 flagged

0.3

Indicators of compromise (SHA-256)

1ae067285b235f683f0db410e52f272dfa7bfb626a4407e6d6d91550e3c11afb

f25bc44a20f24a6175d3cab4807e490c5275039f699b72b79a76b7e03ea4d255

afdfe0e984ef4e0a0370d75a06c0004f9b12242bddbabd35d02b37dafe9c5fb2

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05737RLUA-2024-10256RLUA-2026-08147

References

Credits

ReversingLabs · finder

Detect & block this

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