Which versions of rootxproxytest are malicious?

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

How do I remediate rootxproxytest if I installed it?

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

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

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

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

Malicious package

rootxproxytestRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8543

Immediate action

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

gem uninstall rootxproxytest

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f94e3e9c61d6392cdb83446bbbc9967ac03bdaabd05a53e491ae14bb398eb568

aea932d5e850fd2659077957165a0c9fac2ea49c2a047661f5f02ee16e01d438

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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