Which versions of slnprobe5 are malicious?

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

How do I remediate slnprobe5 if I installed it?

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

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

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

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

Malicious package

slnprobe5RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8719

Immediate action

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

gem uninstall slnprobe5

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c1cb71b75b27615f1ff73c1e9d0b1b04a0ff1afb3f6e0fe57f859317f2364478

3ec950a3a7c99136e1d4a018b361b18ecdf4705c81ea16e6cb3444849c74ad93

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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