Which versions of sproxytestgitone are malicious?

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

How do I remediate sproxytestgitone if I installed it?

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

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

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

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

Malicious package

sproxytestgitoneRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8892

Immediate action

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

gem uninstall sproxytestgitone

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d06bfac2a5e0d031838e11fe0c6a55ec8b02042e015d29ec0c8bc55c8e5ddfec

4a583442dc853a4a5504fd462c3b6ae41155aae0fd45afa6f7548ed36ee50287

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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