Which versions of slnsq01 are malicious?

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

How do I remediate slnsq01 if I installed it?

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

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

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

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

Malicious package

slnsq01RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8732

Immediate action

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

gem uninstall slnsq01

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7703f571c54dde11c201e21922fc0835222fcc6473bd2e883b19df227c95f12e

46be16dbe9a1b7216f546ba1f3efd37b6ce8b16bd6b25abf71492e31af16c2f8

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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