Which versions of zzfadgivar11 are malicious?

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

How do I remediate zzfadgivar11 if I installed it?

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

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

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

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

Malicious package

zzfadgivar11RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9947

Immediate action

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

gem uninstall zzfadgivar11

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e195d14fed506d82d6d8c980546f9e1339d2fcb3a2176bfa8cf5b46b12c59019

fbb543753834b3af63b67ecdd19758a7e4ff0c97ab3fc49d61c2d987e5c910a0

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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