Which versions of slnbxwiltsbk are malicious?

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

How do I remediate slnbxwiltsbk if I installed it?

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

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

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

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

Malicious package

slnbxwiltsbkRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8650

Immediate action

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

gem uninstall slnbxwiltsbk

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

233b64e96e9b1ef1cb2383d64158f60f9ced8261cb331185767d6f7b6ffcfcbc

5747ed3f2bf86d2717a90c1c6d28e3ea6c5e1d703c1fedb88a2fa870904f6b94

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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