Which versions of v26zzgbqvirfx are malicious?

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

How do I remediate v26zzgbqvirfx if I installed it?

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

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

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

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

Malicious package

v26zzgbqvirfxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9089

Immediate action

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

gem uninstall v26zzgbqvirfx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

cc696c868a5d4e436d8364baec2681d3c55074d3bb4fb85342d5fdee5f7d9a51

89434629c0731749dc761f37060c79270578827c4c0cb6cacb897650e4337ae5

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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