Which versions of tryd1zz are malicious?

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

How do I remediate tryd1zz if I installed it?

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

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

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

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

Malicious package

tryd1zzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9017

Immediate action

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

gem uninstall tryd1zz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

50e7f4ea09f74ce941ab052195caa839edb296d345a9cc3e445dc1d4f08d8ad0

058f784f77341c897dda1599951c468b2f5a0e97608cccbe9d1b22558bad4427

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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