Which versions of zjiasearch2 are malicious?

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

How do I remediate zjiasearch2 if I installed it?

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

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

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

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

Malicious package

zjiasearch2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9601

Immediate action

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

gem uninstall zjiasearch2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

4f99fe7da800964ce91d9366bd75d61d1ae7557ecfb2c84aff3cceb7fc397c4a

a30c44741249e944f310b044bb7729c5e2d6d76bf7e1fa0f91187ab785a96c61

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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