Which versions of testproxyxx are malicious?

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

How do I remediate testproxyxx if I installed it?

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

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

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

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

Malicious package

testproxyxxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8988

Immediate action

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

gem uninstall testproxyxx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a0cac1a151a14dd773fbeb1a713122bc5b938fbbd7ac5f5155a47a6e3dd4669a

809b24dfe8f1f2d4bf34e371503d77435c936e8be575f8ac96a21ed9ca318d1c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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