Which versions of hgpathr3 are malicious?

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

How do I remediate hgpathr3 if I installed it?

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

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

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

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

Malicious package

hgpathr3RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7736

Immediate action

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

gem uninstall hgpathr3

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8296211dc3e791c8d8cd285a4eca21e4f69c0a51fdb47320fda9750d273d2b25

a6f9d7d94881eebb5ab138602d75598403459b2c0b0234d23d909d1ad79ac157

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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