Which versions of slnsq07 are malicious?

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

How do I remediate slnsq07 if I installed it?

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

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

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

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

Malicious package

slnsq07RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8738

Immediate action

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

gem uninstall slnsq07

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

622ddeec083c8f105765f189aa77acd878b72fac1ebfcc50a49ef85f6e490f79

ac2ec0235a3102ccf5b8fb5068819da03507cab7d06e3aef39f8b414470e786e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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