Which versions of slnprobe9 are malicious?

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

How do I remediate slnprobe9 if I installed it?

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

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

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

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

Malicious package

slnprobe9RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8723

Immediate action

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

gem uninstall slnprobe9

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7cba1b41442c761831c7c0ee6fe60c07e6070a2dce03be06ef3896115e371db8

098ec78e91e660718ad2efa771ecf59a0c161d980c2585ae4edff6624dff3874

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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