Which versions of slnbrbtiqwcw are malicious?

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

How do I remediate slnbrbtiqwcw if I installed it?

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

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

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

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

Malicious package

slnbrbtiqwcwRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8646

Immediate action

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

gem uninstall slnbrbtiqwcw

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

02e1e0576b6af09fe820e84ef6f5600360b54c84d60175ee8a2b4e83731b59f7

dafc0f50cf12724fe698572348153283f75a8ab0b07c80dfab40237a06b52350

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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