Which versions of zjia23 are malicious?

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

How do I remediate zjia23 if I installed it?

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

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

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

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

Malicious package

zjia23RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9597

Immediate action

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

gem uninstall zjia23

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3dcd7515b80f1585ed4d74ad914d1d0efadd01c4ce902a944b56b38d10191ea1

8a8766fdaa888a35ad68559f78a5e8f542e7e101979bb053cbcd03a412dc56c6

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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