Which versions of slnprobe14 are malicious?

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

How do I remediate slnprobe14 if I installed it?

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

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

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

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

Malicious package

slnprobe14RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8703

Immediate action

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

gem uninstall slnprobe14

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5a4a046c7f2c6f53f1bd49f48ee61ed4eabd166ac5f081fd183bb78451892bdc

1e0ca2485e380f160d352345127a6d65cebd602265f167e327b135a440486f6d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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