Which versions of tryb0zz are malicious?

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

How do I remediate tryb0zz if I installed it?

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

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

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

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

Malicious package

tryb0zzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9008

Immediate action

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

gem uninstall tryb0zz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5e636e72c7b7837b6cabc83104b0bea13de7c275ef24314bf6d1d1585437ec4e

7de1094dcf39a75f4afca661703066e69acdb181d93c091a57f58925f5717f40

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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