Which versions of hgpathr6 are malicious?

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

How do I remediate hgpathr6 if I installed it?

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

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

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

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

Malicious package

hgpathr6RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7739

Immediate action

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

gem uninstall hgpathr6

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b172d09546446c53be2401e473dcd746b50efa0a9f6d9ed2fbcfd044627d8273

7d1f52aef2282e2bf80af59ed548a4c94741c47dcf61856ab0bf262db1b5cbf0

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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