Which versions of slnprobe7 are malicious?

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

How do I remediate slnprobe7 if I installed it?

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

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

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

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

Malicious package

slnprobe7RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8721

Immediate action

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

gem uninstall slnprobe7

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

83170fd44995f46239a59ea23cf3e478df1f12debd331bf45d1151c808baafdf

1f0c82a3a616a6b912bed95210c83fc63a047730e1c16665b3581803dea46822

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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