Which versions of zsgsearch1 are malicious?

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

How do I remediate zsgsearch1 if I installed it?

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

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

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

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

Malicious package

zsgsearch1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9788

Immediate action

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

gem uninstall zsgsearch1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d0a1efbb32233c1ca84bd383d6ac1b3ca86ad15023d4da9b1310699c60eb36a4

0445410eeb3a6a8a2a39a2d034c51beb3263b5d8c377fa9f0b97a0775de8b928

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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