Which versions of tryd2zz are malicious?

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

How do I remediate tryd2zz if I installed it?

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

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

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

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

Malicious package

tryd2zzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9018

Immediate action

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

gem uninstall tryd2zz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c678daffdb8e134822ee3c443b0f59fb0b943ec7e3e53d906a0b5f828e44e09b

f33fc908cc5bc8f3acda5e0278dba51ca85d51be8d3f227277279f02abdd7f6a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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