Which versions of gamer-stats are malicious?

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

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

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

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

Yes — gamer-stats is associated with the RLMA-2024-05734, RLUA-2024-10253, RLUA-2026-08140 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 gamer-stats across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for gamer-stats (version 0.2.5).

Malicious package

gamer-statsRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in gamer-stats (RubyGems)

MAL-2024-6928

Immediate action

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

gem uninstall gamer-stats

Malicious versions

1 flagged

0.2.5

Indicators of compromise (SHA-256)

8f7c5a97eb80ab186700551ca11035cfbcc600447dbe20306201229f13de9bcd

56dd763816e0d9c9c2054b74112276d1d49a9223bf20ca1068d5ff1ed97b52d7

70dcac12bae64d9c5a71785d71f29bbe83f3a1b2360960fab7beff3874702a17

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05734RLUA-2024-10253RLUA-2026-08140

References

Credits

ReversingLabs · finder

Detect & block this

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