Which versions of v12zzgbqvirfx are malicious?

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

How do I remediate v12zzgbqvirfx if I installed it?

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

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

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

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

Malicious package

v12zzgbqvirfxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9075

Immediate action

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

gem uninstall v12zzgbqvirfx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

20d0b9c30047ac21478435e959a76c27d767873f49c5ae37f5e1b1a9eab37a87

0820cbb8bbdc1d50dcdd2c198ae4d23a4f44b1ce1163a1ef2567568c7dc2a04b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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