Which versions of retryqq5 are malicious?

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

How do I remediate retryqq5 if I installed it?

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

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

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

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

Malicious package

retryqq5RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8506

Immediate action

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

gem uninstall retryqq5

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5732a5a43fa27a3e9612c943b091cbf77560442ab44edebc72bf104584609e96

3112e72fed71b69565c31035256b53b75c3db289a2ccae56e30371b5377d1dc8

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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