Which versions of slncabcxyz are malicious?

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

How do I remediate slncabcxyz if I installed it?

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

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

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

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

Malicious package

slncabcxyzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8652

Immediate action

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

gem uninstall slncabcxyz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

024120d81598e1b26cc9ad70ad5db90563cd2665a470c46ef9defae6e56246dc

1d75673b1c7e7a4dd02623c3774a55ef1d81198cdecfc640bf147e990904c711

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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