Which versions of zvbzr0rygmzwp45 are malicious?

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

How do I remediate zvbzr0rygmzwp45 if I installed it?

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

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

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

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

Malicious package

zvbzr0rygmzwp45RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9813

Immediate action

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

gem uninstall zvbzr0rygmzwp45

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

044aaf5b9ffd6bbfb3cb81e47cb78fd1c35a774edaa8ce8c21404db159fc7598

896b54f981ebe32d2a623d50630fb26722a6874edb7c7d7ef2406a2443be2cda

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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