Which versions of slnprobe1 are malicious?

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

How do I remediate slnprobe1 if I installed it?

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

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

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

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

Malicious package

slnprobe1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8698

Immediate action

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

gem uninstall slnprobe1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b170f486f1755aad48beab608f6bd7349730ea0078c98fa512cea973e362c274

e66c0a38fed03320f2be593e1711a002a08f640c776cfdb11b40dc4d10c04e24

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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