Which versions of zrgvq3b2f are malicious?

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

How do I remediate zrgvq3b2f if I installed it?

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

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

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

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

Malicious package

zrgvq3b2fRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9737

Immediate action

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

gem uninstall zrgvq3b2f

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c447f76de3b27d363f2e0f4ee482d6a97def8f72d0e6c3e8e2d3b7261eecc990

cada8b54b6a649034d7e5e2af7775e36d8ddc50017bc90dbbb91d9d81587e504

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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