Which versions of slnprobe19 are malicious?

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

How do I remediate slnprobe19 if I installed it?

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

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

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

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

Malicious package

slnprobe19RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8708

Immediate action

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

gem uninstall slnprobe19

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

201e76bcf98b250b70998bf36a5b479089cf516291415d090924fa7e8a939227

99f37ba9f285079cd8e46ca4e20b25b25132d50a506c39d787ee05403e139bd4

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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