Which versions of slnmid9000 are malicious?

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

How do I remediate slnmid9000 if I installed it?

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

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

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

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

Malicious package

slnmid9000RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8694

Immediate action

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

gem uninstall slnmid9000

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f47a9da5cd07e1b276f820e60f8836b5c4eb66a4853652cd6c6cb343bca651b2

259d790367d7e0747cb5b3fc805397aadd8b90cad124fa63a16b5783cad7d768

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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