Which versions of zrgvhe14c are malicious?

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

How do I remediate zrgvhe14c if I installed it?

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

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

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

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

Malicious package

zrgvhe14cRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9724

Immediate action

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

gem uninstall zrgvhe14c

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

4960ccf21250ade973aee9817c631f2dedf38d71e91d3c4f3f045aa01bb1b5ea

7c4c62307a7b4a64e664dac4741170832a30f5f47b92e75ce9afcc07497a4e7b

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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