Which versions of retryqq2 are malicious?

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

How do I remediate retryqq2 if I installed it?

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

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

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

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

Malicious package

retryqq2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8503

Immediate action

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

gem uninstall retryqq2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

95770f073c8c565fd8b2b71639ceef068e5b9d2c2057b7d432f4d596f9c01eed

30662cd200a53c7d6e302f3db466a47141ef02be4de75de8d110e2ebbadc2d9c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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