Which versions of zrgvf4ace are malicious?

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

How do I remediate zrgvf4ace if I installed it?

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

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

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

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

Malicious package

zrgvf4aceRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9714

Immediate action

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

gem uninstall zrgvf4ace

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d57fb92f4fa985e5da359bb16fe14af9f6a699092f0c37f0dab077d17cb3d599

fa820c267c8afcb13cb21c57dd3e626fad500066888e463c4c98d32b6055a5ed

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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