Which versions of slq29388 are malicious?

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

How do I remediate slq29388 if I installed it?

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

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

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

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

Malicious package

slq29388RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8773

Immediate action

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

gem uninstall slq29388

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

a862faf4a7f9913d031d7e5c1a446e4a3afd7f62fe16943ff2f00ba376176e31

cb1d4d0ca98a1a3e26caaad2e2532cd5942f8af3a3fd59afa96cedbffae5a915

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for slq29388 (version 0.0.2).
If you installed it — respond
Remove slq29388 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 slq29388 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. slq29388 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-03424RLUA-2026-09322

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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