Which versions of hgprobe28069 are malicious?

The following RubyGems versions of hgprobe28069 are flagged malicious: 0.0.125608. Treat any of these as compromised.

How do I remediate hgprobe28069 if I installed it?

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

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

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

Search your lockfiles and build artifacts for hgprobe28069 (version 0.0.125608).

Malicious package

hgprobe28069RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in hgprobe28069 (RubyGems)

MAL-2026-7744

Immediate action

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

gem uninstall hgprobe28069

Malicious versions

1 flagged

0.0.125608

Indicators of compromise (SHA-256)

84f9e0ee2aa04f30b23f3931f3ea863e57aa0f94a06554bfaca5b060d7cea3fe

2cdfba28daa484678bedaf848c06bfb44950eddf4ee0210488bc069f72d39cf0

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02395RLUA-2026-08193

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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