Which versions of slnprobe20 are malicious?

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

How do I remediate slnprobe20 if I installed it?

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

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

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

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

Malicious package

slnprobe20RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8710

Immediate action

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

gem uninstall slnprobe20

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

de652012c57c3cdb00fe4320cc4cf7b49d2208ad09a3553a514bb9b1a053d3dd

b578a8df05c728e4b71b5296a8412fad17fa645ca4b092629950d4937e559628

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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