Which versions of slnfive8155 are malicious?

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

How do I remediate slnfive8155 if I installed it?

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

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

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

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

Malicious package

slnfive8155RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8682

Immediate action

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

gem uninstall slnfive8155

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ef39ea88f69c088ec9d03d3c22641d4f94b14eccf3bcb65b18e99eb09090dc30

eb25df46e6be5edd5899520d97d86e6cad022a83c06fcb3ad0710c4c0bb45fe5

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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