Which versions of trye2zz are malicious?

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

How do I remediate trye2zz if I installed it?

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

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

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

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

Malicious package

trye2zzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9023

Immediate action

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

gem uninstall trye2zz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

13af88c1e5826b7a38e7d432e9cab2a77b86afd7d8be1ce196649dfaffa400b6

f268aa0092db5a8e174fa7b8d372bce99f8d7dc21b2da996befe00932a210fc7

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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