Which versions of slnprobe15 are malicious?

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

How do I remediate slnprobe15 if I installed it?

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

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

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

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

Malicious package

slnprobe15RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8704

Immediate action

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

gem uninstall slnprobe15

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

14a6dfa70a6d19805f7db28c21c0b82399ef4e724f447429a40ebaa2d793f7b9

d6490bd56876a53129a315e83624c55fce8211d7b69b2f93e51bb15a4de76a63

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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