Which versions of testfoo_proxy are malicious?

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

How do I remediate testfoo_proxy if I installed it?

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

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

Yes — testfoo_proxy is associated with the RLMA-2026-03623, RLUA-2026-09547 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_proxy across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for testfoo_proxy (2 malicious versions).

Malicious package

testfoo_proxyRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

testfoo_proxy is a confirmed malicious RubyGems package (MAL-2026-8972) that executes malicious code on install (malicious versions 0.0.1, 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in testfoo_proxy (RubyGems)

MAL-2026-8972

Immediate action

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

gem uninstall testfoo_proxy

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

9e938afc471d8c29b071d4528bdfaadbc60ad7d3e22856986d3611e43bcc05b6

b5fe95c27fbce635e6a1d57fd2fce503efc1ad740de83b88a9d33ad467a2b4d2

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-03623RLUA-2026-09547

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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