Which versions of v3zzgbqvirfx are malicious?

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

How do I remediate v3zzgbqvirfx if I installed it?

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

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

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

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

Malicious package

v3zzgbqvirfxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9090

Immediate action

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

gem uninstall v3zzgbqvirfx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2d4f8c7de045ce7b1d5d6f601e2bc4a4dec31a1928d37262b99209bcf13f7ea7

1c98dcbbd784cd68b8b73d38860589a43f7dfd2d27093a9627223872a4b568d3

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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