Which versions of slq19408 are malicious?

The following RubyGems versions of slq19408 are flagged malicious: 0.0.2. Treat any of these as compromised.

How do I remediate slq19408 if I installed it?

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

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

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

Search your lockfiles and build artifacts for slq19408 (version 0.0.2).

Malicious package

slq19408RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

slq19408 is a confirmed malicious RubyGems package (MAL-2026-8771) that executes malicious code on install (malicious version 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in slq19408 (RubyGems)

MAL-2026-8771

Immediate action

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

gem uninstall slq19408

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

a1d0cb734e75ce4dab224f5e62234bed75dc57182f421ce6d6c190c39879d16a

f6cbd16221c245397dd87e3bf0de803a214530d84000329fc9d9e6e720960894

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for slq19408 (version 0.0.2).
If you installed it — respond
Remove slq19408 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 slq19408 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. slq19408 on RubyGems has been identified as a malicious package (version 0.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-03422RLUA-2026-09320

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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