Which versions of slq28641 are malicious?

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

How do I remediate slq28641 if I installed it?

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

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

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

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

Malicious package

slq28641RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8772

Immediate action

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

gem uninstall slq28641

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

13bb5a91399a178a253b66448f2b7633f59e25482ec828cc885de9898f7e73ed

c054eba1edee3929d69c3e09b3b095783496b26bca252869e103635755d4f8e1

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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