Which versions of slnmid11000 are malicious?

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

How do I remediate slnmid11000 if I installed it?

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

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

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

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

Malicious package

slnmid11000RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8687

Immediate action

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

gem uninstall slnmid11000

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5a907e25c545f7a5d418e8718020dab6f1fefaeb27ff87102d19b4d6f7151a32

fc2e1a3733575551e3d9cbc67297ff0066d93032e091474a43ee6c039d92cb63

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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