Which versions of v22zzgbqvirfx are malicious?

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

How do I remediate v22zzgbqvirfx if I installed it?

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

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

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

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

Malicious package

v22zzgbqvirfxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9085

Immediate action

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

gem uninstall v22zzgbqvirfx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c0b023bb9f2806fc34985a3966ebb351bb6027e4a7200aee1a954dc2d6cb074e

031ec52bddfd2f4c8a9b1ba92a88e90d169e53ea7ca5784bb7e0efe081e9a072

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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