Which versions of testprox52736 are malicious?

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

How do I remediate testprox52736 if I installed it?

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

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

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

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

Malicious package

testprox52736RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8985

Immediate action

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

gem uninstall testprox52736

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

d4f9ac654ed099eab7cd8197ecc286a2e0f5d3690c640cb3dc4939e2e4e19808

5f63848781507a001c9e4e68792313d1ed9f26a130cc818fa0fe814a450c4ed3

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for testprox52736 (2 malicious versions).
If you installed it — respond
Remove testprox52736 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 testprox52736 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. testprox52736 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-03636RLUA-2026-09560

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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