Which versions of slnmid9500 are malicious?

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

How do I remediate slnmid9500 if I installed it?

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

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

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

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

Malicious package

slnmid9500RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8695

Immediate action

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

gem uninstall slnmid9500

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

21a90616417de20abd518d248421648f66057a76e2f2aa3c62f82a25b68a658e

6eabedcdb2cf2b2c925f663507c1af6a73b5622e70f2e0975c2150c329ec1292

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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