Which versions of v21zzgbqvirfx are malicious?

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

How do I remediate v21zzgbqvirfx if I installed it?

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

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

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

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

Malicious package

v21zzgbqvirfxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9084

Immediate action

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

gem uninstall v21zzgbqvirfx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c15b0bd7851702c2cc2f9b1468814bf1935c91b40d08c8f20220da33a13ab454

a555e9f32565e69899771a4aae862f2c3915db048c38cb87a428978b427af3c8

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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