Which versions of zrgvrawbz are malicious?

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

How do I remediate zrgvrawbz if I installed it?

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

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

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

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

Malicious package

zrgvrawbzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9745

Immediate action

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

gem uninstall zrgvrawbz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

87ee154276514c34b5b7df83fb87a3deddbfb4c70a63d4216db6e7e1ba6b438d

ffb4b7cc5eda7b6871e807ee9acb767a524b59de8cf0a32da7655f190b2a3956

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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