Which versions of zjia22 are malicious?

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

How do I remediate zjia22 if I installed it?

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

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

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

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

Malicious package

zjia22RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9596

Immediate action

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

gem uninstall zjia22

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5099f0eeaeabb30fa5898c55c28a40a0910aedfa98e1e632227bdb579e06802d

9b3c1ca0ebff08d04c095c886f411057f63dd90508875de158f82663ea9dc22a

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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