Which versions of hgrangex4 are malicious?

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

How do I remediate hgrangex4 if I installed it?

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

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

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

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

Malicious package

hgrangex4RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7748

Immediate action

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

gem uninstall hgrangex4

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8fc62ac867cc6e795dcb342985f8f9c8cdf11b80d6e9c97074cff231e8d4b858

910a0b62a1c32fffc04e4aa8f97485bce31822a2781a0cf42a0694e657d6dc92

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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