Which versions of wlambzr are malicious?

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

How do I remediate wlambzr if I installed it?

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

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

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

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

Malicious package

wlambzrRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9371

Immediate action

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

gem uninstall wlambzr

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

84bf8b95ea8f1dd322e62477fce82121bf82589519eda2f70d349dbc7540e15f

0ef5e27ac9791b4340ab8fe47822404a1b50d263cee9730ea43537a8257751e4

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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