Which versions of zjgview5 are malicious?

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

How do I remediate zjgview5 if I installed it?

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

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

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

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

Malicious package

zjgview5RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9593

Immediate action

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

gem uninstall zjgview5

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6d105cb344df2361c569ebabed356968bb9829d04999be5ec0b477384f9f307a

92fce2cb88b6a9c2b6e876476ca6ff90517d4e0e955acd47a48d9b161bfd3675

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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