Which versions of zrgvbif79e are malicious?

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

How do I remediate zrgvbif79e if I installed it?

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

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

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

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

Malicious package

zrgvbif79eRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9710

Immediate action

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

gem uninstall zrgvbif79e

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

fc31e1a16a27c3e4520377f24044b7b081705cfed1642d93e26faf0af79dbdc5

155c980a43387e3eceb7b1d61c800e5f8a6a027d52ca75caaefaa74284ddf85d

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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