Which versions of slnprobe16 are malicious?

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

How do I remediate slnprobe16 if I installed it?

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

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

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

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

Malicious package

slnprobe16RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8705

Immediate action

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

gem uninstall slnprobe16

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

048e31cadcddc35caee4cd612001286ef6c65ebc98267b5ef4883b1868d9a55a

f82d16499da02790b02db4beef45d01db92bedc2852066dbc2bc4ddf1955aa75

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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