Which versions of retryqq13 are malicious?

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

How do I remediate retryqq13 if I installed it?

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

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

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

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

Malicious package

retryqq13RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8500

Immediate action

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

gem uninstall retryqq13

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6ee846f677bc8f0e509593c35902ec2dff4af4b2a0af41dc9a937dddefdca511

2495bf7b2dede5d60c4e2acf325c2fade116ce0b3fdb607b9e272618ed109878

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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