Which versions of v24zzgbqvirfx are malicious?

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

How do I remediate v24zzgbqvirfx if I installed it?

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

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

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

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

Malicious package

v24zzgbqvirfxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9087

Immediate action

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

gem uninstall v24zzgbqvirfx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b29a80f9bd6af0163d9715f9079a29e0600bf3a5447e04f8768c6d2cab08c415

728a44a286220388291bef676ad51bd363475a663d8b75a6dc4171a3ec5302f0

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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