Which versions of slnprobe18 are malicious?

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

How do I remediate slnprobe18 if I installed it?

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

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

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

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

Malicious package

slnprobe18RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8707

Immediate action

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

gem uninstall slnprobe18

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

dc295ea70da286bd0df8aa8a784321304ce5d65ca81cbb47ec437bec8dc0e5f6

c2181f814808f4b1aa73e6dc76edf9fb44ad44732c76846a8801c02cd185f9cf

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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