Which versions of slq34178 are malicious?

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

How do I remediate slq34178 if I installed it?

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

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

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

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

Malicious package

slq34178RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8774

Immediate action

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

gem uninstall slq34178

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

c743b7c76bf685b249bd7e13b2f3a430526398d5b7da74d7a9a8daf2047a8507

a307348caf7da2cf7d38b43d1b87c09aea5e42dc61586e1d9fa8c0a104398d07

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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