Which versions of slnprobe12 are malicious?

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

How do I remediate slnprobe12 if I installed it?

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

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

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

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

Malicious package

slnprobe12RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8701

Immediate action

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

gem uninstall slnprobe12

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

adb26290cbcde1a8c27323457225799790144ee4438398f1508b7bc3dcfa0c33

0f10094d0ceacbea2fad59125e69397cdbf3c55f223f1112d1ca4f1189ecbf45

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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