Which versions of slnciguegg are malicious?

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

How do I remediate slnciguegg if I installed it?

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

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

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

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

Malicious package

slncigueggRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8662

Immediate action

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

gem uninstall slnciguegg

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

333ab15c9a221bc53b056c8ecb2531df1d55686645887573cd6feaf1929d8263

b093147cfb0a0714eab1583864b714de08ae693b071d65e1ded78598a6228dd7

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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