Which versions of southhgjina245 are malicious?

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

How do I remediate southhgjina245 if I installed it?

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

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

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

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

Malicious package

southhgjina245RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8826

Immediate action

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

gem uninstall southhgjina245

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7c3fca0be6aa959a3566a7bb386de75a037b9865f2fc418cdf3204c0fb586bfd

2cdbdd48b0dc35338b2ec6bcd9dc99d0598d5f87129d7dfa4b35cb89be976537

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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