Which versions of slnprobe13 are malicious?

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

How do I remediate slnprobe13 if I installed it?

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

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

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

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

Malicious package

slnprobe13RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8702

Immediate action

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

gem uninstall slnprobe13

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

326421425eb00766001b2ee6a8054d7ce9f1feaf1e36dc78f75640a123925432

ac067950d688084cb9e07c83efce595d1bc3465f4e7fe704ec7734d1281ea174

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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