Which versions of tryd0zz are malicious?

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

How do I remediate tryd0zz if I installed it?

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

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

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

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

Malicious package

tryd0zzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9016

Immediate action

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

gem uninstall tryd0zz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0b77b2f55ab2ab8dbea5650c1029811320b056380d00ab9fcad19ced1691d676

5bde1cfd811c39b7d569c71b74a7f6586124a8d5c2fe254132fa1211037b1f3c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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