Which versions of southproxy2 are malicious?

The following RubyGems versions of southproxy2 are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate southproxy2 if I installed it?

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

If southproxy2 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 southproxy2 part of a known attack campaign?

Yes — southproxy2 is associated with the RLMA-2026-03491, RLUA-2026-09389 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 southproxy2 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for southproxy2 (version 0.0.1).

Malicious package

southproxy2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

southproxy2 is a confirmed malicious RubyGems package (MAL-2026-8840) 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 southproxy2 (RubyGems)

MAL-2026-8840

Immediate action

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

gem uninstall southproxy2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

cb47628e029d2787683062425d169af0c1d2a101f732c6d2b1cfa7e8d0ab1a53

fcaf27646551bcf07fc9e6ea37c25f3fbffd7e9d34da082c7486b8934e11197e

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for southproxy2 (version 0.0.1).
If you installed it — respond
Remove southproxy2 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 southproxy2 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. southproxy2 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-03491RLUA-2026-09389

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks southproxy2-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