Which versions of slnsq12 are malicious?

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

How do I remediate slnsq12 if I installed it?

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

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

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

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

Malicious package

slnsq12RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8743

Immediate action

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

gem uninstall slnsq12

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d0ae7db901f790de1dbf0f5f0dfba34fd2fd468602e52b92ac43881147fd5241

f1907aa932a4fe6ed704a9d9f518a71d0c7bacec4979fae9530df6c5c7b96a81

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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