Which versions of hgprobe16819 are malicious?

The following RubyGems versions of hgprobe16819 are flagged malicious: 0.0.550831. Treat any of these as compromised.

How do I remediate hgprobe16819 if I installed it?

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

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

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

Search your lockfiles and build artifacts for hgprobe16819 (version 0.0.550831).

Malicious package

hgprobe16819RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in hgprobe16819 (RubyGems)

MAL-2026-7740

Immediate action

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

gem uninstall hgprobe16819

Malicious versions

1 flagged

0.0.550831

Indicators of compromise (SHA-256)

00aaa1f42a8d1867f9ea063a79e836507a3fba0342dff2ffa8da4585d4def1a4

fe446ece10da8d213a8b6af5f43bcd80b63005003c42218c32ed5ddee05065e1

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02391RLUA-2026-08189

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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