Which versions of slncuebwsw are malicious?

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

How do I remediate slncuebwsw if I installed it?

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

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

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

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

Malicious package

slncuebwswRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8666

Immediate action

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

gem uninstall slncuebwsw

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f4f471fff93fe775bac42ce193a9610611ca1916b61575b976aea40a1e528517

4972f5a31025e17847f3f40d1350c5f7391eedb9d983f21dc8de1083384400da

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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