Which versions of tryf1zz are malicious?

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

How do I remediate tryf1zz if I installed it?

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

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

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

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

Malicious package

tryf1zzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9027

Immediate action

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

gem uninstall tryf1zz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ef8f9f19f3fb66ca763a75470dfc47ec3bdc9785fb0970fac1ff6d7ee6542eef

4b7ba6d917512ee869d9c68d079a141567001381585c1f1b1e06d7260ad90558

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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