Which versions of trye0zz are malicious?

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

How do I remediate trye0zz if I installed it?

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

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

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

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

Malicious package

trye0zzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9021

Immediate action

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

gem uninstall trye0zz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b99455e4635f384853ecd4cbbec92fb3e8b6fe42fa2ecd213af0dd4828efcfc0

e394281c1323839e4b9f20f7fd8465e555bd3b48e160f509c3bf6bb09862a0be

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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