Which versions of slnsouth1 are malicious?

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

How do I remediate slnsouth1 if I installed it?

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

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

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

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

Malicious package

slnsouth1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8730

Immediate action

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

gem uninstall slnsouth1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

66c1795187aea25c587ced60386aad2a44c7d1f7117207c6b5f11a480375a1ea

00768c6ddd23395ae6da0285d88c8cd7a9a4253ced5e31d4282929f640dafa83

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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