Which versions of trya3zz are malicious?

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

How do I remediate trya3zz if I installed it?

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

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

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

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

Malicious package

trya3zzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9005

Immediate action

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

gem uninstall trya3zz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

bd217a32dd2dc6bbca11d1f7a53cdbeae48c9b02b280941ff7124f3a6ac8e379

7ed383a8026bdc86bc7c64188f417dd5f6ea7025fe936eeb728a8445d9ecbb82

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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