Which versions of slncriiuuy are malicious?

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

How do I remediate slncriiuuy if I installed it?

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

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

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

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

Malicious package

slncriiuuyRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8664

Immediate action

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

gem uninstall slncriiuuy

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ff680722425dd5c6a2960e415551f7e2bb6d91150a46ec59f1cecb7b58fb6b47

ab76352269478a9865d743bd4e5ded724d2e94a14e43bcb096492d46a1225463

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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