Which versions of tryf5zz are malicious?

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

How do I remediate tryf5zz if I installed it?

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

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

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

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

Malicious package

tryf5zzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9031

Immediate action

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

gem uninstall tryf5zz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

56c3138f07149a8307027ee421561a57772bc11eda35b60dc8936e0218655696

af1ebc198068780de962df76c183a8953f68c5863b49405ce78d661ef9804c10

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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