Which versions of slnprobe17 are malicious?

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

How do I remediate slnprobe17 if I installed it?

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

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

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

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

Malicious package

slnprobe17RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8706

Immediate action

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

gem uninstall slnprobe17

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3eb7f2a7d04baad87596bbf228c60f16fe63c7d664520fcf8dd6055fe50131a1

531ac67544916f77727da223d873ab0d17a67b06f5f292e6104f6c1554d662c0

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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