Which versions of slnprobe22 are malicious?

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

How do I remediate slnprobe22 if I installed it?

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

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

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

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

Malicious package

slnprobe22RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8712

Immediate action

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

gem uninstall slnprobe22

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b42894a7ed76cbd80b5d8ec0960234344e7d5fe3f80c4641cede4a88e81becd5

4b676ea349e87f815bc2b609dc6d9017be9c3404b2d5620d0411bdd2215c8be7

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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