Which versions of sprox-c160-3git are malicious?

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

How do I remediate sprox-c160-3git if I installed it?

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

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

Yes — sprox-c160-3git is associated with the RLMA-2026-03531, RLUA-2026-09437 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-3git across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for sprox-c160-3git (version 0.0.1).

Malicious package

sprox-c160-3gitRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

sprox-c160-3git is a confirmed malicious RubyGems package (MAL-2026-8880) 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-3git (RubyGems)

MAL-2026-8880

Immediate action

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

gem uninstall sprox-c160-3git

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

42e47837e6a8b754bfbde24d5ff92becdece69f87b009c4fa091f4b37e9631bd

49e7986136033ea56ee0fecad554534b0f0924e3c4dcacd0df099948c056834a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks sprox-c160-3git-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