Which versions of retryqq15 are malicious?

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

How do I remediate retryqq15 if I installed it?

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

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

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

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

Malicious package

retryqq15RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8502

Immediate action

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

gem uninstall retryqq15

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3235f6c7756861c7fbe144f67bb44e62f031fe2ba35744a7757d9f5306ca86a9

ca2f608b8a47203abd4838b8a0b911938c0ba880a553c2abf7f0704c79eb9b01

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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