Which versions of hgpathr5 are malicious?

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

How do I remediate hgpathr5 if I installed it?

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

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

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

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

Malicious package

hgpathr5RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7738

Immediate action

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

gem uninstall hgpathr5

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

49065547dff7cc4b28c00908927aa0f355d99a75904e28fe6bbdad3a9344109f

facab57da8f0e0d0bb1423bc464941beb5f4fcd923a44e16eab2e6825eb99db0

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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