Which versions of zrgvf6b4a are malicious?

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

How do I remediate zrgvf6b4a if I installed it?

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

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

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

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

Malicious package

zrgvf6b4aRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9715

Immediate action

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

gem uninstall zrgvf6b4a

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

780600ec826820d6d42cb7713313ce530ae533cd28cfcc8ad959ab1bef4b24fb

6474a31255f36237171c1f69165e8aff8ead4a86f96b6c8a52b5e91bba972c4c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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