Which versions of zzfadgivar13 are malicious?

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

How do I remediate zzfadgivar13 if I installed it?

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

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

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

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

Malicious package

zzfadgivar13RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9949

Immediate action

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

gem uninstall zzfadgivar13

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a3c4eaf1815f947c88f4953f444eacc34c66300c14b1922a05d21c6f34c1a3e2

41d80bacb30e305649ff7f9dc2ad4ea452930cc349e862406a64f658cff41b57

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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