Which versions of zjsrch2 are malicious?

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

How do I remediate zjsrch2 if I installed it?

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

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

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

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

Malicious package

zjsrch2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9614

Immediate action

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

gem uninstall zjsrch2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ddcc4ba9e91a5be973450296c6e12f3b979123713654497cd5a5822f3a83803f

15c1a050ef35274002bed3bafb78cae41bdc40d8b3ee377fca5550f0feb038b2

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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