Which versions of v9zzgbqvirfx are malicious?

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

How do I remediate v9zzgbqvirfx if I installed it?

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

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

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

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

Malicious package

v9zzgbqvirfxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9096

Immediate action

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

gem uninstall v9zzgbqvirfx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ec8a4731d9b16787222d4e1aa9de0c0f73b0cf5df543443169cdfc59c001f7db

e7c4caea031d5f6233e4b759476732c858af3d3c530e311d7ad83bd2dffa59e1

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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