Which versions of gozzz are malicious?

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

How do I remediate gozzz if I installed it?

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

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

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

Search your lockfiles and build artifacts for gozzz (2 malicious versions).

Malicious package

gozzzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

gozzz is a confirmed malicious RubyGems package (MAL-2026-7719) that executes malicious code on install (malicious versions 0.0.1, 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in gozzz (RubyGems)

MAL-2026-7719

Immediate action

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

gem uninstall gozzz

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

ea8f148f5228a7f909f1120f21480d64828eed32bf8d15ea36c2297635182108

a47cc70460a9a6031e3e034c7b795f980ace16be08e5028413660a7021d01099

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for gozzz (2 malicious versions).
If you installed it — respond
Remove gozzz 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 gozzz 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. gozzz on RubyGems has been identified as a malicious package (versions 0.0.1, 0.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-02370RLUA-2026-08161

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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