Which versions of zrzggsearch are malicious?

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

How do I remediate zrzggsearch if I installed it?

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

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

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

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

Malicious package

zrzggsearchRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9757

Immediate action

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

gem uninstall zrzggsearch

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ad1d95f5ce8e2484916f6dc37f483edd7d9aa5a6dd80e64b488729fd81df4ea0

04e5700c73b19f8d4ddf5fce7e42a23991b49e775b61cd97d0e37b429050c590

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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