Which versions of sprox-c160-4mod are malicious?

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

How do I remediate sprox-c160-4mod if I installed it?

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

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

Yes — sprox-c160-4mod is associated with the RLMA-2026-03539, RLUA-2026-09445 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-4mod across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for sprox-c160-4mod (version 0.0.1).

Malicious package

sprox-c160-4modRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

sprox-c160-4mod is a confirmed malicious RubyGems package (MAL-2026-8888) 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-4mod (RubyGems)

MAL-2026-8888

Immediate action

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

gem uninstall sprox-c160-4mod

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d9340c26400bc650c1ce5f77c83902883ad99bde9874b0cacea75e750275da99

07879cdf787f0bfa8379512a67930a6c410f500bb5ec54509c404d29570228b9

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks sprox-c160-4mod-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