Which versions of retryqq8 are malicious?

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

How do I remediate retryqq8 if I installed it?

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

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

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

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

Malicious package

retryqq8RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8509

Immediate action

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

gem uninstall retryqq8

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

34c0aa5594b1e2f26a0c54b092e7a1ed7110e5c2166047a97b72a9d4a6d209de

4ff7487dde6d6b6266fe2de1c4e5b7a56ab249111f33cddcd457db126138d8bf

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for retryqq8 (version 0.0.1).
If you installed it — respond
Remove retryqq8 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 retryqq8 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. retryqq8 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-03160RLUA-2026-09047

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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