Which versions of slnsq05 are malicious?

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

How do I remediate slnsq05 if I installed it?

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

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

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

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

Malicious package

slnsq05RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8736

Immediate action

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

gem uninstall slnsq05

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f6f8a6d44ad01a89b964ce0ef022f562dfbf2d7f7ab80e5a8cbffbfcaf2664d2

e1f14679a8b920b6ce2d9838c8625f837180913e3c086b3ada9195c2f446b4ed

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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