Which versions of tryf7zz are malicious?

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

How do I remediate tryf7zz if I installed it?

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

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

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

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

Malicious package

tryf7zzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9033

Immediate action

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

gem uninstall tryf7zz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

fb69034e2744e83d6bbf8a9f866de44ad90ae1118790a0777c4aca9d170de91f

0ccc889e14260e74a2f9c60a9fed0c867696b58a760e44e9478855c33309c8f8

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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