Which versions of zrhgrange are malicious?

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

How do I remediate zrhgrange if I installed it?

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

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

Yes — zrhgrange is associated with the RLMA-2026-04406, RLUA-2026-10344 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 zrhgrange across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for zrhgrange (version 0.0.1).

Malicious package

zrhgrangeRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

zrhgrange is a confirmed malicious RubyGems package (MAL-2026-9755) 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 zrhgrange (RubyGems)

MAL-2026-9755

Immediate action

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

gem uninstall zrhgrange

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

18b0b0f0116df939c810d34624c80cb5642dfc40f2bb44357a34f8808b912b74

f00cb2e5a3bd71c80f96bb80ce3600cba28959f324e6e487e94dc0f7835f9b92

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for zrhgrange (version 0.0.1).
If you installed it — respond
Remove zrhgrange 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 zrhgrange 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. zrhgrange 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-2026-04406RLUA-2026-10344

References

Credits

ReversingLabs · finder

Detect & block this

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