Which versions of slnprobe25 are malicious?

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

How do I remediate slnprobe25 if I installed it?

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

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

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

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

Malicious package

slnprobe25RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8715

Immediate action

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

gem uninstall slnprobe25

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5f9648be77afcac6557b0db9b893162bafd0cc077732c724e74bda3c97fd708c

2f0093a1955d6eefb9b54f249fdaf4c293b1e861f8ccd90c262759064dd38435

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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