Which versions of slnprobe0 are malicious?

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

How do I remediate slnprobe0 if I installed it?

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

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

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

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

Malicious package

slnprobe0RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8697

Immediate action

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

gem uninstall slnprobe0

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b5fd99aa91d2912dcaeec28a91d02400708a3e173a578dea45bcab03cec49301

aa05b09ace5e9fe6e352bb29866f7306523c702a716656126f98048ab012ad9d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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