Which versions of slnmid6000 are malicious?

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

How do I remediate slnmid6000 if I installed it?

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

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

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

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

Malicious package

slnmid6000RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8688

Immediate action

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

gem uninstall slnmid6000

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

26d9427592148fbae6cc1fe662664c504e71128e9c1c2e3d7bb6d72cd1c9082a

8af76543decb668c39841a7575947bc0de559d2146673c9125acf1ea24c2ecd5

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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