Which versions of slnfive8150 are malicious?

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

How do I remediate slnfive8150 if I installed it?

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

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

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

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

Malicious package

slnfive8150RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8681

Immediate action

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

gem uninstall slnfive8150

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0b0db73ba3211b7c80f1047658acd65724f420b2f717121c643bc11b1ab5257e

f3cffcfc0dfca1e2a570d475f5d56b6eee5d1c0b9370b57d7634a96561152659

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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