Which versions of retryqq6 are malicious?

The following RubyGems versions of retryqq6 are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate retryqq6 if I installed it?

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

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

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

Search your lockfiles and build artifacts for retryqq6 (version 0.0.1).

Malicious package

retryqq6RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in retryqq6 (RubyGems)

MAL-2026-8507

Immediate action

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

gem uninstall retryqq6

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f344e09021847ba21d4c9a05b77232e334e68810f7069c5f96f641a02ee063c1

d8ff309f9ac3e2e7020e9d3390d31430a36ef909a7ee403d24976741ef01f245

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-03158RLUA-2026-09045

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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