Which versions of sprox-c160-2hg are malicious?

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

How do I remediate sprox-c160-2hg if I installed it?

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

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

Yes — sprox-c160-2hg is associated with the RLMA-2026-03526, RLUA-2026-09432 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-2hg across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for sprox-c160-2hg (version 0.0.1).

Malicious package

sprox-c160-2hgRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

sprox-c160-2hg is a confirmed malicious RubyGems package (MAL-2026-8875) 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-2hg (RubyGems)

MAL-2026-8875

Immediate action

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

gem uninstall sprox-c160-2hg

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

58fba6dbf1c45b11cb7e1ae2c7857255470f973f08604caf04a029a643c0e90b

e70382a5456b66d8230701ba74062d010ba8c6885e0cc5e20524dc237dbb0a50

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks sprox-c160-2hg-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