Which versions of retryqq9 are malicious?

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

How do I remediate retryqq9 if I installed it?

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

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

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

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

Malicious package

retryqq9RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8510

Immediate action

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

gem uninstall retryqq9

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

dad6e0ca7aee5463dae2a12e04cfdf8cc8d1572d359e3875001f94992fe811d2

919df44a576fb5554b181a5444ba1d8405273581f22653a4342767612683d0b4

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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