Which versions of slnmid7000 are malicious?

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

How do I remediate slnmid7000 if I installed it?

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

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

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

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

Malicious package

slnmid7000RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8690

Immediate action

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

gem uninstall slnmid7000

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

bff33acae984c388a01b88a92cbefcecde7390bf7c441b85cab284d44d628ec5

8e021a9c500d033173a99e0ea269a4b37a76be529c9245664b975fbfe5fd448f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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