Which versions of zjimg80 are malicious?

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

How do I remediate zjimg80 if I installed it?

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

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

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

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

Malicious package

zjimg80RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9603

Immediate action

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

gem uninstall zjimg80

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a102a7144279c1fe45d258794494872e523d5c48ea7a4ed0496b0b11c82a52a2

706e906cb1255132beb2aa5b8578da8f72b4832f0dafd3f9614bc522df4acc80

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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