Which versions of slncmuayli are malicious?

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

How do I remediate slncmuayli if I installed it?

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

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

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

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

Malicious package

slncmuayliRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8663

Immediate action

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

gem uninstall slncmuayli

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7a092c25342c8ad332226319b8f22ee28f29f1218c65348d711d5e76b7cd4def

596b9cdd9d6539f9eab0ffea0fa2ba214c2586d7e383a2ca7a9b01fb716fe3bb

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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