Which versions of wandbzrx are malicious?

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

How do I remediate wandbzrx if I installed it?

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

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

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

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

Malicious package

wandbzrxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9141

Immediate action

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

gem uninstall wandbzrx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

500c195d98d1686f388a729c10907930abd28bb210f783aa991dc31ffdcff839

e1ae7125b1dac87259d3b17c08ac3944424e993def306ac76fbc84a51164d1df

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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