Which versions of slnprobe23 are malicious?

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

How do I remediate slnprobe23 if I installed it?

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

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

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

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

Malicious package

slnprobe23RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8713

Immediate action

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

gem uninstall slnprobe23

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

26f4b74f65c38cd87ab72110843a12a2ec6c80860c1c7269b62830038028f004

b35901b468e14b37d6f92f287b7d5afe9491ebc532354f87adddac1cdcce8fa9

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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