Which versions of zjiasearch1 are malicious?

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

How do I remediate zjiasearch1 if I installed it?

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

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

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

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

Malicious package

zjiasearch1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9600

Immediate action

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

gem uninstall zjiasearch1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2473e38e19c7fab0d935758e00f69e3d5cccb8b936d2dfe8c4b4d0fd66731a41

e1877e776e4f7ea07e1f2bafadc934d2861a7d232d095dc5dcbd78e9e1584033

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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