Which versions of github_release-stats are malicious?

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

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

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

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

Yes — github_release-stats is associated with the RLMA-2024-05741, RLUA-2024-10260, RLUA-2026-08152 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 github_release-stats across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for github_release-stats (version 0.0.2).

Malicious package

github_release-statsRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in github_release-stats (RubyGems)

MAL-2024-6935

Immediate action

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

gem uninstall github_release-stats

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

bb49a5ca588b7695830681d71ecb9dcf78095737c33d81cb6e4e399ecdf487d3

032d8b216ef081f1df8bbd18625049376c7b73465d050d1e931d50be25ae474e

bca8af647ec450df5270e078a8d6102d0c2b7f8deb65ead110bd1f5da94ba9dd

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05741RLUA-2024-10260RLUA-2026-08152

References

Credits

ReversingLabs · finder

Detect & block this

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