Which versions of vanityzzgbqvirfx are malicious?

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

How do I remediate vanityzzgbqvirfx if I installed it?

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

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

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

Search your lockfiles and build artifacts for vanityzzgbqvirfx (2 malicious versions).

Malicious package

vanityzzgbqvirfxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

vanityzzgbqvirfx is a confirmed malicious RubyGems package (MAL-2026-9109) that executes malicious code on install (malicious versions 0.0.1, 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vanityzzgbqvirfx (RubyGems)

MAL-2026-9109

Immediate action

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

gem uninstall vanityzzgbqvirfx

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

45633ae04fdb5ac6f6f22ea9a51f59cc45f367b33cf856bb9b086ed9f55aef04

233e2f426837b1fd96f02b15bd6f2468fa5b39da586118e2ad6dba8f632297c1

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for vanityzzgbqvirfx (2 malicious versions).
If you installed it — respond
Remove vanityzzgbqvirfx 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 vanityzzgbqvirfx 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. vanityzzgbqvirfx on RubyGems has been identified as a malicious package (versions 0.0.1, 0.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-03760RLUA-2026-09689

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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