Which versions of slnsq10 are malicious?

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

How do I remediate slnsq10 if I installed it?

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

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

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

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

Malicious package

slnsq10RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8741

Immediate action

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

gem uninstall slnsq10

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

877f53c0ed8167327adf46d300d135566a59a9aba9c494eedcef9748cbd13be2

e129d8c940c91672137f0a451cf928d0e9ae0c99f220d827144faf6ebab29ac6

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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