Which versions of tryf4zz are malicious?

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

How do I remediate tryf4zz if I installed it?

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

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

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

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

Malicious package

tryf4zzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9030

Immediate action

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

gem uninstall tryf4zz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3c314b488de97a6632f795bde167188e69c46b18c26577759fb138d2c166177b

6055e7beb8365a99447658347b247784abcceea41554334f53b78195a15219d8

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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