Which versions of southip1 are malicious?

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

How do I remediate southip1 if I installed it?

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

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

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

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

Malicious package

southip1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8828

Immediate action

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

gem uninstall southip1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c2bc0702af64e272ad35c4263aac41a65ec0588d10155721db04a86f6ee20162

16f04c5252ed094c368f8554eceb3682ea9e1be98cfaf4710993e4194c8cef21

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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