Which versions of slnprobe26 are malicious?

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

How do I remediate slnprobe26 if I installed it?

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

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

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

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

Malicious package

slnprobe26RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8716

Immediate action

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

gem uninstall slnprobe26

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

4459ccaa4521c2863256e94e8a7163c03645ea9f721aa000618e5a74f30711e8

4ed07015e658b3ec23bd8cd24a808fbcb76254ca0a1c948d514f926fbc6c68a9

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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