Which versions of slnprobe6 are malicious?

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

How do I remediate slnprobe6 if I installed it?

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

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

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

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

Malicious package

slnprobe6RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8720

Immediate action

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

gem uninstall slnprobe6

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

184137aa743a47d6e76c2131fe1b733c3e93120fa0e423fcd79644afbfaddd8c

c8aa3eeee8972afa7c65cb68266e9956733dfd156a62dd8443bab562865dffd0

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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