Which versions of v19zzgbqvirfx are malicious?

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

How do I remediate v19zzgbqvirfx if I installed it?

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

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

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

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

Malicious package

v19zzgbqvirfxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9082

Immediate action

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

gem uninstall v19zzgbqvirfx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

83c672c77051c1a0bb00f165f300988471778630db8b71dbe3eb8b4efac4aefd

ed08b1709e1ab40b1579f57b2787bf9e6d6f98c37d2f2e601aa759ba9bec35ae

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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