Which versions of retryqq3 are malicious?

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

How do I remediate retryqq3 if I installed it?

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

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

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

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

Malicious package

retryqq3RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8504

Immediate action

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

gem uninstall retryqq3

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f964989a93c6836a21c0db605fa4cb4553166c41a687d8f89c8dae8e2b20fba9

03e882ffc2f815855cb1298682703aa447575c4505678265ae40a28d7ca3e254

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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