Which versions of retryqq12 are malicious?

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

How do I remediate retryqq12 if I installed it?

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

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

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

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

Malicious package

retryqq12RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8499

Immediate action

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

gem uninstall retryqq12

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

86415a8d637d7602b1b3a7a11521dc81e75d1f4b14a0bd3684bdc3d3586f566c

2a3712138bd65a15209b986a9f7ce66712885b9bd5624fa1cf2dc4dd72aaf908

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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