Which versions of slnssearch03 are malicious?

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

How do I remediate slnssearch03 if I installed it?

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

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

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

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

Malicious package

slnssearch03RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8747

Immediate action

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

gem uninstall slnssearch03

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2dfd0233799b0a8ceadcc0bfce6da8eae91e1358baa0c4fd11f00260d65b7466

697335e8c776bf7e68fcb6b39412acbf880a1dc35c08e08d55edebda425c93ec

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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