Which versions of slnaabcxyz are malicious?

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

How do I remediate slnaabcxyz if I installed it?

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

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

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

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

Malicious package

slnaabcxyzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8638

Immediate action

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

gem uninstall slnaabcxyz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

21215aaef9d8167fdc62858b1b93b8ff15848089b3f8d473ae47d807adb00508

ecdd86ee97579a402af28a7531d8a86325f8444753b375fb67d4d1fe7268f827

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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