Which versions of v15zzgbqvirfx are malicious?

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

How do I remediate v15zzgbqvirfx if I installed it?

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

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

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

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

Malicious package

v15zzgbqvirfxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9078

Immediate action

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

gem uninstall v15zzgbqvirfx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

418cca074f7742977953e1422888f0c45b2a1e94c2a1c929bdf8ca2242ae6def

2d0b1ac2654075d495d367c2e3edd0627451a010b85366a59122d03ceda8c8f5

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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