Which versions of zzfadgivar04 are malicious?

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

How do I remediate zzfadgivar04 if I installed it?

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

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

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

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

Malicious package

zzfadgivar04RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9940

Immediate action

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

gem uninstall zzfadgivar04

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

74f2303dc439f724d94e74a0ecfd11d05eda012cadac8306fe5b2fb434f7a577

959c2df8a226c7b2671ab93ecac3ef5c13c3c0bab5a28e81cd1b319f780bf881

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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