Which versions of tryf0zz are malicious?

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

How do I remediate tryf0zz if I installed it?

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

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

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

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

Malicious package

tryf0zzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9026

Immediate action

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

gem uninstall tryf0zz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

33cbfba0748b561c220c5265c1eede1f41ffbf643d47c1b40e86cee77eb56d48

6cb1b64ba1c187f0a1dcbd19439be9054522ee9e846b93cdc9ffed3cf945b49d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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