Which versions of hgrangex8 are malicious?

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

How do I remediate hgrangex8 if I installed it?

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

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

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

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

Malicious package

hgrangex8RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7752

Immediate action

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

gem uninstall hgrangex8

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

cf3e30a36dde41e1971beb699dff579a6b7692a46af344f8e1f82216bc6b5e50

8277761fd8b6ab19369f6b44758e45bf909346171be28847b9a7ad947155f062

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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