Which versions of slq39369 are malicious?

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

How do I remediate slq39369 if I installed it?

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

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

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

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

Malicious package

slq39369RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8775

Immediate action

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

gem uninstall slq39369

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

088b1d02e2fd1edc0d031db1dc6975e8bdfc1aedd1d745aaad3dd62b664fbe4f

5a6dda8e058743920ea0e7c146cc3112848b2af9b5531af2df3cc0f337a34377

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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