Which versions of hgprobe26718 are malicious?

The following RubyGems versions of hgprobe26718 are flagged malicious: 0.0.799406. Treat any of these as compromised.

How do I remediate hgprobe26718 if I installed it?

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

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

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

Search your lockfiles and build artifacts for hgprobe26718 (version 0.0.799406).

Malicious package

hgprobe26718RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

hgprobe26718 is a confirmed malicious RubyGems package (MAL-2026-7743) that executes malicious code on install (malicious version 0.0.799406). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in hgprobe26718 (RubyGems)

MAL-2026-7743

Immediate action

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

gem uninstall hgprobe26718

Malicious versions

1 flagged

0.0.799406

Indicators of compromise (SHA-256)

39550b02cbcb1e263d9b6d8f87888b5a1db981c22c62620e120781adc8a94d56

c3ff551d36f8a3ad50b2ff231e49989dbfe077747b741e6f0ff0e0d648b25210

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for hgprobe26718 (version 0.0.799406).
If you installed it — respond
Remove hgprobe26718 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 hgprobe26718 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. hgprobe26718 on RubyGems has been identified as a malicious package (version 0.0.799406 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-02394RLUA-2026-08192

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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