Which versions of retryqq4 are malicious?

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

How do I remediate retryqq4 if I installed it?

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

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

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

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

Malicious package

retryqq4RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8505

Immediate action

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

gem uninstall retryqq4

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

224934542777cd758bcec49062d1ee4ae29e7f35f97f4b46c44f2a90708e3944

4fcce04f0c7c856ea57e7840502508cb23282b4c5cb3dd1776c8a7dd9d4e19e5

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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