Which versions of hgpathr1 are malicious?

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

How do I remediate hgpathr1 if I installed it?

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

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

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

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

Malicious package

hgpathr1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7734

Immediate action

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

gem uninstall hgpathr1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

27e4e2b3861cb68297e70e47bdb2a91104665555c132685020d41852909b1d0b

3d9121c41291d8dbbe6523690b5f94aabc3301f6e935e55531807e9ab39d2730

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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