Which versions of zrzoffice80 are malicious?

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

How do I remediate zrzoffice80 if I installed it?

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

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

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

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

Malicious package

zrzoffice80RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9769

Immediate action

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

gem uninstall zrzoffice80

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9a303eb9023353b8f59feaca128add861279f33d152bb8a4cb52266a58c50d94

406664e8249a9a6c5a7aaf8c72c8a782441ddf32a1ec08640a07fa58d61e8a05

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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