Which versions of xyzbr are malicious?

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

How do I remediate xyzbr if I installed it?

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

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

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

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

Malicious package

xyzbrRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9551

Immediate action

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

gem uninstall xyzbr

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e74dd9845559ff396cebfaa148d05461f0b9eba7f027fcd4710095ac08f1a748

f1f2a90d8fb0d749e0563d678dbf44e69558f8fb8775d6d162a2c911e4370878

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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