Which versions of sprox-c160-1bzr are malicious?

The following RubyGems versions of sprox-c160-1bzr are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate sprox-c160-1bzr if I installed it?

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

If sprox-c160-1bzr 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 sprox-c160-1bzr part of a known attack campaign?

Yes — sprox-c160-1bzr is associated with the RLMA-2026-03517, RLUA-2026-09423 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 sprox-c160-1bzr across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for sprox-c160-1bzr (version 0.0.1).

Malicious package

sprox-c160-1bzrRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

sprox-c160-1bzr is a confirmed malicious RubyGems package (MAL-2026-8866) 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 sprox-c160-1bzr (RubyGems)

MAL-2026-8866

Immediate action

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

gem uninstall sprox-c160-1bzr

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

979612adab2d6278a88839b793cf5be2ff4a9b70ec259288c3088c7bfc29bcd6

14eabbdd1dda8d29d89cc47c3dc223a8b0d81b537b58751f698b45688aaf83de

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for sprox-c160-1bzr (version 0.0.1).
If you installed it — respond
Remove sprox-c160-1bzr 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 sprox-c160-1bzr 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. sprox-c160-1bzr 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-03517RLUA-2026-09423

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks sprox-c160-1bzr-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