Which versions of tryf2zz are malicious?

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

How do I remediate tryf2zz if I installed it?

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

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

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

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

Malicious package

tryf2zzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9028

Immediate action

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

gem uninstall tryf2zz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d1a66e17a57033334b846bdc85937f59d580709771940eeb5ccc2599cacbadda

ce3bb3194877634340373f24c28185ad0baaa4cf98ecc71b38de87df7417682b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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