Which versions of slnccduioc are malicious?

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

How do I remediate slnccduioc if I installed it?

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

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

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

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

Malicious package

slnccduiocRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8656

Immediate action

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

gem uninstall slnccduioc

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5e5a7d25f8727ccd12bf4c4dd823c785fceab00cb2744b7968518794534a3d67

ad462424f1ee25a8562cc5f3d714cdd1ce6f5620762b88ddc1d2e52c3ba367fe

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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