Which versions of trya4zz are malicious?

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

How do I remediate trya4zz if I installed it?

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

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

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

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

Malicious package

trya4zzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9006

Immediate action

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

gem uninstall trya4zz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d082d9131c6642671c2f36cac39cd3b534b262936c2742f0bbebf183e9c75e39

41e7a820153a03e7795d877a8f0d0a93ed22fd6846e19ffaf1f735c52a5253e4

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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