Which versions of zrzoffice10 are malicious?

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

How do I remediate zrzoffice10 if I installed it?

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

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

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

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

Malicious package

zrzoffice10RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9765

Immediate action

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

gem uninstall zrzoffice10

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ed7f671516cf46fc65301093384074a4d7a4a428e3a6c48f29b36467268d5339

890ae56d1082eb6268d3ae05cbe62a09e8ca5613eb7137b0eca109d0d7da659c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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