Which versions of southproxyhg are malicious?

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

How do I remediate southproxyhg if I installed it?

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

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

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

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

Malicious package

southproxyhgRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8843

Immediate action

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

gem uninstall southproxyhg

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a7fae9ee5eedaf57cc829b6b33d75d4a7abe7c3dd5e20835d716817c4d134ff0

b27e16c4e6b1f7e40d7f8399660ebb399fc744c64c7114f8868d80bed1af1b12

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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