Which versions of retryqq10 are malicious?

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

How do I remediate retryqq10 if I installed it?

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

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

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

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

Malicious package

retryqq10RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8497

Immediate action

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

gem uninstall retryqq10

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

91ac8717184132832df6073ec7cf4d471229bac6306fbb59fa93a93a77af1329

03155ba7997d32b981e1c06fc830b3f29ff9c3eb364f701ade48d6b7c180cc08

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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