Which versions of slnmid8000 are malicious?

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

How do I remediate slnmid8000 if I installed it?

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

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

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

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

Malicious package

slnmid8000RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8692

Immediate action

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

gem uninstall slnmid8000

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c4dee92c1b28accf7f7107426653ebe18be851e34ea78edb543d0ebda70adb2a

fe6e009783a4d00e907df0c7a7df67163c90f17d5e4dbfe235a28ec3c3814271

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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