Which versions of slnmid10000 are malicious?

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

How do I remediate slnmid10000 if I installed it?

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

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

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

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

Malicious package

slnmid10000RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8685

Immediate action

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

gem uninstall slnmid10000

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

dfaa243a50d56e46193e0933109e57760584fb12f1200a27fc6c8a982c6c3052

945add7b7fee599fcea4800630bb8e2b53b8d806eea8abc7da4dfc406e638c45

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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