Which versions of v7zzgbqvirfx are malicious?

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

How do I remediate v7zzgbqvirfx if I installed it?

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

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

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

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

Malicious package

v7zzgbqvirfxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9094

Immediate action

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

gem uninstall v7zzgbqvirfx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

70cc92641fa8a39798a8aa4842b1abc01dc802b5c63cd4f647c465ded6bfbfb4

925e0447fd28e2f652b19ed67fa91fb0cb2045b1a223082f4565db9a552ebb06

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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