Which versions of slnprobe21 are malicious?

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

How do I remediate slnprobe21 if I installed it?

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

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

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

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

Malicious package

slnprobe21RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8711

Immediate action

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

gem uninstall slnprobe21

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1998525060bc8eac73072b95dd6d31d3fc7a777ba0fd1f4f3c9711fb069133df

d1757c11417ab4b4f341e1ce2ef7079bb04a1632822d5742af7abf8067c61ab0

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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