Which versions of trye4zz are malicious?

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

How do I remediate trye4zz if I installed it?

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

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

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

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

Malicious package

trye4zzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9025

Immediate action

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

gem uninstall trye4zz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

fbc05a6d452bdb6527a4bf00790d8050009f6f2bd295788d6ce8e81024a9f26c

65d3a218c5e2c22983be3e7569b27f24dc93fc583609ddcf4f4c638d2b239874

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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