Which versions of hgrangex9 are malicious?

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

How do I remediate hgrangex9 if I installed it?

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

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

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

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

Malicious package

hgrangex9RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7753

Immediate action

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

gem uninstall hgrangex9

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

329d5707b1d322ea9f8c94a14b6399ae7840b7e5f7c234c92dee18b6059a68d1

8347e114e6e7d9b5b369107cf512666bdb57ac066af63ad0a41cd5aeb031cdfb

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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