Which versions of zjiamd3 are malicious?

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

How do I remediate zjiamd3 if I installed it?

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

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

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

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

Malicious package

zjiamd3RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9598

Immediate action

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

gem uninstall zjiamd3

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6a5658acfa43c8b9200354e83f3389cec0a2f080b2a886a1a5bcfc04df09b493

dee3a8760de994f0ea606246b1f8e49cf8b14fb9dcd32997ea1d0506a93e3050

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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