Which versions of southmeet8320 are malicious?

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

How do I remediate southmeet8320 if I installed it?

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

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

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

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

Malicious package

southmeet8320RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8831

Immediate action

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

gem uninstall southmeet8320

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0ddece048466fa8bb8a7e514a213d110bd1ae729f1a7683f198d23292789304a

ec37765d34ca5ca750fed04d20f2ea0bae58bde1847a0997f9d43525c6c1da88

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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