Which versions of trya5zz are malicious?

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

How do I remediate trya5zz if I installed it?

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

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

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

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

Malicious package

trya5zzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9007

Immediate action

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

gem uninstall trya5zz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ad689461d5451ebeb88a2fad569d644c264cb42367910d602ea797a54936eb25

917286160453ef3a81b7d7c9e87d586e79e0336b33ec7af77145deeee4ebb878

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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