Which versions of wandbzrroot are malicious?

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

How do I remediate wandbzrroot if I installed it?

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

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

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

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

Malicious package

wandbzrrootRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9140

Immediate action

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

gem uninstall wandbzrroot

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

036d5fe1f825c61b3a63245bc04c1ea536bf702bf1cfb516f2ba9883a301d316

4f60ef49b5e16ef69c24e7ad83d8eaf7f3870396e385f2ae2cc36b5d17b3112d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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