Which versions of testfoo_proxy2 are malicious?

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

How do I remediate testfoo_proxy2 if I installed it?

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

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

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

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

Malicious package

testfoo_proxy2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8973

Immediate action

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

gem uninstall testfoo_proxy2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e5718aa620bf777921d4245ce1b7b226bf2ed912bb0387bdda9290002d5d85ac

087cd1543c9e4ba30d9e248f6b9718323fca066f8e0155cc9732af0ddcac40ce

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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