Which versions of sproxytesthgone are malicious?

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

How do I remediate sproxytesthgone if I installed it?

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

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

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

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

Malicious package

sproxytesthgoneRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8893

Immediate action

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

gem uninstall sproxytesthgone

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8af0cf005b9d5a7fc4ce886ea166e7365959c6932e90c9e730e3068826c4b7b6

ed56dcbafc6a808018ef020ba291249c86deb60b0cf9bf3d292213377a68758c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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