Which versions of slnctoiblt are malicious?

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

How do I remediate slnctoiblt if I installed it?

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

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

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

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

Malicious package

slnctoibltRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8665

Immediate action

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

gem uninstall slnctoiblt

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5c5f280d2266e4cb23bf03cb3afc2b354a6b86474d2e721c8aea47fff755fc2e

b90a021144680cd46d95c853bf3e35ed4069354584e8a24de1960e4757fe1926

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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