Which versions of retryqq7 are malicious?

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

How do I remediate retryqq7 if I installed it?

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

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

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

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

Malicious package

retryqq7RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8508

Immediate action

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

gem uninstall retryqq7

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

fd37ecaab58b7314f85673b2753a1f3a18a89b0816a3097029131cc9985a0b4f

207c9d91bd58190ccb8e4c5a53c8f3d0c74d5e2775a58d770030442d62d7a740

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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