Which versions of slx55008 are malicious?

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

How do I remediate slx55008 if I installed it?

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

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

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

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

Malicious package

slx55008RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8799

Immediate action

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

gem uninstall slx55008

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

145d0ca8334bebf56f29975017ef44d207f1d6a1aa2e095526ca1bd1846bf504

114d38b31bec707c9a539f7bb835b89bd57fa80ed3758181b01db14491a9e3dc

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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