Which versions of zrzx2bfe6e are malicious?

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

How do I remediate zrzx2bfe6e if I installed it?

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

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

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

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

Malicious package

zrzx2bfe6eRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9773

Immediate action

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

gem uninstall zrzx2bfe6e

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5d25c439eeebb26eb09262f4fa55080354d326b55466ff3c7161684268eae349

731d6aa3d285702392d8223297cc63e04dbe040c5838c0acb314574ca39bc382

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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