Which versions of v13zzgbqvirfx are malicious?

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

How do I remediate v13zzgbqvirfx if I installed it?

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

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

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

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

Malicious package

v13zzgbqvirfxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9076

Immediate action

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

gem uninstall v13zzgbqvirfx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d86d8e1573c2546aed6f9fbdf6154d457a565376d142af29d37a78ee3f94103b

310af694b28fe9f5d52f025dbde494ead7169e47bdd27c7412240c6c06bcfb7d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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