Which versions of tryd4zz are malicious?

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

How do I remediate tryd4zz if I installed it?

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

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

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

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

Malicious package

tryd4zzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9020

Immediate action

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

gem uninstall tryd4zz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d879a3042f7f05b124e70b3013d40881f8e7ef4b62324ee25e9dba2caa3761f4

cafdde7b26b5ae003ed715179e17be26513a83a27acaaee883d02abc14bfa81b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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