Which versions of sproxytestbzrone are malicious?

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

How do I remediate sproxytestbzrone if I installed it?

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

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

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

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

Malicious package

sproxytestbzroneRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8890

Immediate action

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

gem uninstall sproxytestbzrone

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5c0747db51bfe16cb2265b6c820a31bf45c61570f540e2ea35c4bbd0898b19c5

31775f9103e8599598dba37292cd95dc8fc7dd5320292f5a46463663e73dd7a7

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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