Which versions of tryf8zz are malicious?

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

How do I remediate tryf8zz if I installed it?

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

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

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

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

Malicious package

tryf8zzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9034

Immediate action

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

gem uninstall tryf8zz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f1c5dfddf941b7d9a7e72967e7ea829f5633cf192bbf9b804a4bbd4c3195c2aa

e7f1a83c754ddba5fe6a75e40dd93634216159f542ff55340d7481e09cc3c88e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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