Which versions of zzfadgivar02 are malicious?

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

How do I remediate zzfadgivar02 if I installed it?

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

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

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

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

Malicious package

zzfadgivar02RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9938

Immediate action

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

gem uninstall zzfadgivar02

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2cbdb10ed7f1cd3e6b0fc0b2752822bc0b2ec0ac4f9ca653a20b68ac08c3ceca

af248c4f0a047dd08ee5dbc2fe5e9e2ccecc34f94f76c97bb34a14944568f9ec

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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