Which versions of tryc4bzz are malicious?

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

How do I remediate tryc4bzz if I installed it?

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

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

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

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

Malicious package

tryc4bzzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9013

Immediate action

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

gem uninstall tryc4bzz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e41403acdc2a56988a60c0218b53233cc805dedf49296debdfb462dfc9a5c8af

b453549e2f59a8e83ed9dcef2a7d8f455446aae2e88cb3e3cef0ffa426030353

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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