Which versions of slnsq04 are malicious?

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

How do I remediate slnsq04 if I installed it?

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

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

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

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

Malicious package

slnsq04RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8735

Immediate action

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

gem uninstall slnsq04

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d12d12e8898303f3f6cfca023dc363036c0523c9341816a35b45f1298702ffac

ef20641d06ac1b619a0c2b36adb8bc2e0c4d3b0eea8ac80b1c672a104dd56206

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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