Which versions of tryc4xzz are malicious?

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

How do I remediate tryc4xzz if I installed it?

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

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

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

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

Malicious package

tryc4xzzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9015

Immediate action

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

gem uninstall tryc4xzz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2f4a345bd75aa4656f70f15568f7143d8fa9973fe7033296833fbd344ba1947a

39fb555ec803e0298fc75f54047ff1fc22bb96c9d6ecdd2d6d4a12707ca99aab

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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