Which versions of zrzoffice50 are malicious?

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

How do I remediate zrzoffice50 if I installed it?

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

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

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

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

Malicious package

zrzoffice50RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9768

Immediate action

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

gem uninstall zrzoffice50

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3d68181ea1bb517f6cf8a2358f4bcb50c5f59645aacab34da671b80d241aeb6b

d25f0dc60c60ef743ac031876f980cf7e4c34a971b9cc8cc67a016becf66eae9

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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