Which versions of v16zzgbqvirfx are malicious?

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

How do I remediate v16zzgbqvirfx if I installed it?

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

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

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

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

Malicious package

v16zzgbqvirfxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9079

Immediate action

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

gem uninstall v16zzgbqvirfx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0dcfb25bcad2bb0a2a7959552f4b11df8eded0b9a89d4eaaccdbe124457d73ac

2f41d39e098ceefc9023bf7cf071cf316e9230f01fc7e22688e80f800d2dcbd0

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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