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

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

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

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

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

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

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

Malicious package

sprox-c160-1modRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8870

Immediate action

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

gem uninstall sprox-c160-1mod

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e2d72dfa137a53fc86d250e4883be5a5d7a6c7c8b9ab1717fb57845dc46b3e8c

cf7ab743c4fa5de9ea3102ef182df90535c63c3a5b6749e8914ca07b8675b726

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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