Which versions of v14zzgbqvirfx are malicious?

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

How do I remediate v14zzgbqvirfx if I installed it?

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

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

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

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

Malicious package

v14zzgbqvirfxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9077

Immediate action

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

gem uninstall v14zzgbqvirfx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a600f24226a5d4fc4f2eff35cf4601f32098b44d46ad9d4a33b1c03aef0ba1d1

a3cc78c833f2671939bd5175f3f093c1e0e0afbe2aecf3edd8b749dbfcd5dba6

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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