Which versions of wwandbzr are malicious?

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

How do I remediate wwandbzr if I installed it?

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

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

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

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

Malicious package

wwandbzrRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9493

Immediate action

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

gem uninstall wwandbzr

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ecea8bd19fcf11d8932b07a1e55e94a4b3294d1f76b5895a7b70060ccc612138

18da0fb557e9ad08082c4dfd363f1f65f3f481dc143cd99546df85defb7db941

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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