Which versions of slnprobe8 are malicious?

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

How do I remediate slnprobe8 if I installed it?

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

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

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

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

Malicious package

slnprobe8RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8722

Immediate action

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

gem uninstall slnprobe8

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b0edcd004e7bb9514f83651866bbe229e02033cee174ff00326d2f055abfe013

a1ae5800938273b812cb53d32f69bcb5441ba93b0ab38b20d8299d813639a784

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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