Which versions of v17zzgbqvirfx are malicious?

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

How do I remediate v17zzgbqvirfx if I installed it?

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

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

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

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

Malicious package

v17zzgbqvirfxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9080

Immediate action

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

gem uninstall v17zzgbqvirfx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3fda8021f63fb9b466feb1ec69d69d41358f937138a611e0d784917c8db8a36b

cc2d7037dac06cc08d86d6d96fb287eb802b42a0ff173220cde173a8a2b1478f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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