Which versions of zrgvq511b are malicious?

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

How do I remediate zrgvq511b if I installed it?

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

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

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

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

Malicious package

zrgvq511bRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9739

Immediate action

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

gem uninstall zrgvq511b

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6b59c9bcbfbb01c0d1b933e0ad2c2523c74ec91d569b0f74ae989fbbb6b2c999

3e868fcbb2cc39dfe7a58753a0d7bb946ed2df0c9e07a59eab0379fd1185fe66

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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