Which versions of zrgvbie2eb are malicious?

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

How do I remediate zrgvbie2eb if I installed it?

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

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

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

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

Malicious package

zrgvbie2ebRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9706

Immediate action

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

gem uninstall zrgvbie2eb

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e63e73f90cc2642c1eab267ab78a4711976688d8035a8f476388730aab0b0a3a

f3845305ebfc99df954d0a51c6dd9e1b6b1694e5b35f98f5992b5191a05e92cc

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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