Which versions of slnsq08 are malicious?

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

How do I remediate slnsq08 if I installed it?

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

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

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

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

Malicious package

slnsq08RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8739

Immediate action

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

gem uninstall slnsq08

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

61f15547550c8262abcdc9d5d2ad17ab69eb2050729adc7be9ca7e496e5514f4

8b4b5fd832a80cc8dcacef00d63ec728955b5cb485362994ffb0df4835eaa4d9

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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