Which versions of southfossj356 are malicious?

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

How do I remediate southfossj356 if I installed it?

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

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

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

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

Malicious package

southfossj356RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8823

Immediate action

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

gem uninstall southfossj356

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d5452f15407a9beda201ad150ff129852c56339e63edc7bb37fdb5226e35be29

f175d3e2731890d66ae2190bb6df80b8027a8c6b9ea50d76e56af0bc5edec13f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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