Which versions of hgrangex7 are malicious?

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

How do I remediate hgrangex7 if I installed it?

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

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

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

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

Malicious package

hgrangex7RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7751

Immediate action

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

gem uninstall hgrangex7

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7474f7eddf8b0f35dc6c42e95439a82ca3d1fbe985a2d588c28b16414dde1411

7ccbdbb11778afdd0e024992ec857eb4bcaffa52be7bb71f7b58841a14425fd2

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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