Which versions of retrylasttry1 are malicious?

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

How do I remediate retrylasttry1 if I installed it?

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

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

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

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

Malicious package

retrylasttry1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8496

Immediate action

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

gem uninstall retrylasttry1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8fff5b6cb6dbe8d7d35b76888ff7df55c4506baa30a40846327f340794e65353

077ea8a363244d90d33871bcc5c0a44137a7a784365eee12866e324e17a2ae60

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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