Which versions of slnprobe11 are malicious?

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

How do I remediate slnprobe11 if I installed it?

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

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

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

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

Malicious package

slnprobe11RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8700

Immediate action

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

gem uninstall slnprobe11

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9e63fd00261361d11d165cca2e0fe9867e04983903e0b6a6ddce076bdb7040ac

cb2a02e5a9c8ce173a4e63ed6bd38564325e8b516798f1d3d6263fdf127579e6

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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