Which versions of v25zzgbqvirfx are malicious?

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

How do I remediate v25zzgbqvirfx if I installed it?

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

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

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

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

Malicious package

v25zzgbqvirfxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9088

Immediate action

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

gem uninstall v25zzgbqvirfx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

74ef67698f483ff2c36d2d77e662dd50c83143cbec0519f4a085fabc898e011e

f62aa7b86acd98e66970372b65f843b4191f32e9917b4831408a8377006a56ce

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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