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

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

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

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

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

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

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

Malicious package

sprox-c160-0hgRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8863

Immediate action

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

gem uninstall sprox-c160-0hg

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

42fffe3ebbc0da1de85515ce152bb152c43af8dad08b1d9b6d115434bf7ea295

be92a76a82210576903f7f1e87e2647efbb802f8f01cef69d3e15732e89d3b53

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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