Which versions of slnmid6500 are malicious?

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

How do I remediate slnmid6500 if I installed it?

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

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

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

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

Malicious package

slnmid6500RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8689

Immediate action

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

gem uninstall slnmid6500

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5d8d99b1f0848dd5e562bff6d2752ed31ee3f86cee6b225ee8dbe31f5169c528

5cbf039a19c3236ddefd19afed762f1494e0bb0858a7580d0ff6eef87aa82d4d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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