Which versions of slnbsmulycfl are malicious?

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

How do I remediate slnbsmulycfl if I installed it?

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

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

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

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

Malicious package

slnbsmulycflRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8647

Immediate action

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

gem uninstall slnbsmulycfl

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ff1021a14968dcc2564ecb6aaaff8e84f557cbbd6a11d7932ec4c5ce6775b133

a7af10f75868710a50768d330e503f459feb050e73f1a734b9c8e20fbe79d775

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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