Which versions of zjia21 are malicious?

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

How do I remediate zjia21 if I installed it?

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

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

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

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

Malicious package

zjia21RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9595

Immediate action

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

gem uninstall zjia21

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

4fa164467604a392beabb94a9b64ea5478af9d925291a14f02c79556c1a84a48

9836137d6ad3fca861bdf861f1ee8aece5af2636c6e14e2f449627e763166f1a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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