Which versions of zjiarange2 are malicious?

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

How do I remediate zjiarange2 if I installed it?

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

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

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

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

Malicious package

zjiarange2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9599

Immediate action

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

gem uninstall zjiarange2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

fdc4069951dff4ba6aef0a5018a49a18aab5b5094738a7c98d9dea2e80571ffb

cd60b583a1bf9b1dfc8d942ef3568e8902490fb253d420686307af1c03ceac6e

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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