Which versions of southproxyfossil are malicious?

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

How do I remediate southproxyfossil if I installed it?

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

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

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

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

Malicious package

southproxyfossilRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8842

Immediate action

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

gem uninstall southproxyfossil

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

26ca943a02afbd733b454b938e6e7e1dec6325fa6d95bd5a662126c02c3231ee

b812e7652b0985cc0559ddb9be81e647acb520a39e1db15f7891479f8b9c12db

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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