Which versions of rootxproxyhg are malicious?

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

How do I remediate rootxproxyhg if I installed it?

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

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

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

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

Malicious package

rootxproxyhgRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8542

Immediate action

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

gem uninstall rootxproxyhg

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9b297545ea5c0ac63be85ebc85b7bdd51c9d5a8d1b95ba357908c0bd45323c40

dbfe8228511f3178c7eb17382ccae31661b87241802152f8431827ce7d39d88f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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