Which versions of hgpathr4 are malicious?

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

How do I remediate hgpathr4 if I installed it?

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

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

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

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

Malicious package

hgpathr4RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7737

Immediate action

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

gem uninstall hgpathr4

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

50843e3e0fdcb930e4d3976d958e05aead614072127a00b186e841bc207ec641

a1bd105bd817eaf080c88021181a03b8665eee642adc68c3dcddbced5dd4de30

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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