Which versions of sproxytestsvnone are malicious?

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

How do I remediate sproxytestsvnone if I installed it?

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

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

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

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

Malicious package

sproxytestsvnoneRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8895

Immediate action

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

gem uninstall sproxytestsvnone

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9d0c522d02f443666015397a38b69451e0836e0566551778f6b6def72653b41e

b8420a1e7b73af35ef71575b2b2cc161c82f79dc728864eebc29c6241a5eac3a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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