Which versions of slnfive8120 are malicious?

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

How do I remediate slnfive8120 if I installed it?

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

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

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

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

Malicious package

slnfive8120RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8675

Immediate action

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

gem uninstall slnfive8120

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1be64ebef24fbca9553d1bdc8736cdf81f71755894e3f3fa241dafc111b699c8

b063e0b0a7ca8d49386dbf3117a455f4f0a1dfeb9549aa20d6a5f1b9e349366e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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