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

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

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

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

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

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

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

Malicious package

sprox-c160-1svnRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8871

Immediate action

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

gem uninstall sprox-c160-1svn

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

77033f7aea762fcda190cb6e16f2308c707a0277d269d04bfef2c3cb02afc9c6

952f298549fd6a6294ab51e1f5ac07ad701d4befdf279184668719f7194337e9

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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