Which versions of hgprobe20548 are malicious?

The following RubyGems versions of hgprobe20548 are flagged malicious: 0.0.858540. Treat any of these as compromised.

How do I remediate hgprobe20548 if I installed it?

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

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

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

Search your lockfiles and build artifacts for hgprobe20548 (version 0.0.858540).

Malicious package

hgprobe20548RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in hgprobe20548 (RubyGems)

MAL-2026-7741

Immediate action

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

gem uninstall hgprobe20548

Malicious versions

1 flagged

0.0.858540

Indicators of compromise (SHA-256)

181193f9684e0b8007eeb4e8d2d158dae0a02ca1c4c0c7e08b36f949b64b3de8

ead5a7d306b103fcdf9997b419894954b94da5fc04543bb2078f33bdb4636349

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02392RLUA-2026-08190

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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