Which versions of sproxytestmodone are malicious?

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

How do I remediate sproxytestmodone if I installed it?

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

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

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

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

Malicious package

sproxytestmodoneRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8894

Immediate action

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

gem uninstall sproxytestmodone

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8e3113ae842ee714bdbeb805f34cc5c734ee9ec4fc01ea14fb9e47827bf542dc

175f4dd0f0f06c9646640d21726cd78522c53e5581ec38e31f06f8e368ff8bcf

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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