Which versions of slnprobe2 are malicious?

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

How do I remediate slnprobe2 if I installed it?

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

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

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

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

Malicious package

slnprobe2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8709

Immediate action

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

gem uninstall slnprobe2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ebb17c3b3354a3036ceff228ee896eac8ead708e6102e377b20fb1800c37c073

d347dee57438ab8715a88fc39ebf98c047bc3c2bfd1da0a49d7317fd0834918d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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