Which versions of hgrangex1 are malicious?

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

How do I remediate hgrangex1 if I installed it?

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

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

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

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

Malicious package

hgrangex1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7745

Immediate action

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

gem uninstall hgrangex1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

65a304b6e8aca83b65c1fe24b7cbd805e2a20511e6fa34ef9216cea962286e13

2bb8c0f08420f4849c80a25dab4cfb86c7435257fca14609ad56290f3835ced9

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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