Which versions of v5zzgbqvirfx are malicious?

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

How do I remediate v5zzgbqvirfx if I installed it?

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

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

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

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

Malicious package

v5zzgbqvirfxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9092

Immediate action

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

gem uninstall v5zzgbqvirfx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6c270e2cff5f5ce0b9e5048243d635f9f4a26ee6f03b6f6eedc7c23e80a0de0a

84e1b3609588fc368e4a462e5aa9f59b029004b3b4119bb2d13f88c72a37d382

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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