Which versions of slnsq09 are malicious?

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

How do I remediate slnsq09 if I installed it?

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

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

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

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

Malicious package

slnsq09RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8740

Immediate action

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

gem uninstall slnsq09

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3e344b26ff4bd4bb37ca64eab85a0f30873e62bff1e0080a5bc92b2c80893e69

d4c8fcfc903f9d1f43f8dc9a230ccc73ff4f713e290662be9517b98ae531e8da

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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