Which versions of tryd3zz are malicious?

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

How do I remediate tryd3zz if I installed it?

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

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

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

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

Malicious package

tryd3zzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9019

Immediate action

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

gem uninstall tryd3zz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a6e42a2ff0946601a78668b521af1b7ed8776bbf3148ffe453a31b301f0eff12

cf70ac4861ca82a5872de0d26479c3bbcec841f33df79858ad43daf28186d92b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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