Which versions of slnprobe24 are malicious?

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

How do I remediate slnprobe24 if I installed it?

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

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

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

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

Malicious package

slnprobe24RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8714

Immediate action

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

gem uninstall slnprobe24

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9eb128be93c75ce2641fa6c930e3c4ea656385b2f8c860ec277275a3643eeb8d

469896331c5124019e8c7490a2cc21c4cef866d88faf63cb54ca0e4263f4c412

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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