Which versions of zrgvbid9be are malicious?

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

How do I remediate zrgvbid9be if I installed it?

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

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

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

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

Malicious package

zrgvbid9beRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9704

Immediate action

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

gem uninstall zrgvbid9be

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

643f9d8abbd20c13ab9a35224ccf0c2fa5befeb48bf024edbe8eca6885a7266d

09a69f7c3280909b60a646d2017a06fa601ade96a04cb29dbb03d2a3e36817e7

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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