Which versions of v10zzgbqvirfx are malicious?

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

How do I remediate v10zzgbqvirfx if I installed it?

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

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

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

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

Malicious package

v10zzgbqvirfxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9073

Immediate action

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

gem uninstall v10zzgbqvirfx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

17916565b94654dc2720ff97445cf124816647a244cceb29c163acd5cbf0a447

a4cebe93f8857adbd5788c8950f67709bdd8952b27c7fd2ddc858e4396723be9

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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