Which versions of southhacks47761 are malicious?

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

How do I remediate southhacks47761 if I installed it?

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

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

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

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

Malicious package

southhacks47761RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8825

Immediate action

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

gem uninstall southhacks47761

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f38e5ab837b80aacfc8ca9a8df9813a7bb06167e3589201b24ebc12a1ebe9522

5ae025dac76feea35d42821b9ddd61eb27372a5dfccb436b873a76c07328e203

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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