Which versions of zrgvff86c are malicious?

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

How do I remediate zrgvff86c if I installed it?

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

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

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

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

Malicious package

zrgvff86cRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9719

Immediate action

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

gem uninstall zrgvff86c

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d1e2eda578ecdf286690e0b8677204bb594978cbf79b3e7b56dca46159154534

5dd4078192d5892ac997455f3479abdbb2feb111ea70bc9b2ab5e99f18b3e8ee

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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