Which versions of halo-stats are malicious?

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

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

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

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

Yes — halo-stats is associated with the RLMA-2024-05745, RLUA-2024-10264, RLUA-2026-08177 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 halo-stats across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for halo-stats (version 1.0.3).

Malicious package

halo-statsRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in halo-stats (RubyGems)

MAL-2024-6939

Immediate action

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

gem uninstall halo-stats

Malicious versions

1 flagged

1.0.3

Indicators of compromise (SHA-256)

0ec527b746309f2c2305b060ac4c184ae6c009d20cf08b1081d637c057d02610

49ccfd1daf6bfd075ce23c9ac1c5a9cd085873f091d6e0fc79273710b2cba2e3

d099625ecb0ec5632198a8d0cd19f5748c416f20815ca888df2cf7fe6c58e8bf

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05745RLUA-2024-10264RLUA-2026-08177

References

Credits

ReversingLabs · finder

Detect & block this

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