Which versions of slnssearch01 are malicious?

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

How do I remediate slnssearch01 if I installed it?

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

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

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

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

Malicious package

slnssearch01RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8745

Immediate action

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

gem uninstall slnssearch01

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8ad4d702475d6e4d6a54e29fc4b54730f8aba0b87be66d07dbba42c987b3ff53

867d6e5a7a32c40af768926c6ba1305028522fe9ddc5379974d70534d672349d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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