Which versions of hgrangex6 are malicious?

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

How do I remediate hgrangex6 if I installed it?

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

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

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

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

Malicious package

hgrangex6RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7750

Immediate action

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

gem uninstall hgrangex6

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7144b64e9b499fed9e86d3ca432d33b7bed67de8bb7268fa212ec924aa4bcf2c

c4825735f6d9f7387c5528f4b451fc329d4c67d62e26930de21b6b3393b94285

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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