Which versions of zzjinavcsgit are malicious?

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

How do I remediate zzjinavcsgit if I installed it?

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

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

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

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

Malicious package

zzjinavcsgitRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9952

Immediate action

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

gem uninstall zzjinavcsgit

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

bf21a77767b158c191a5c627ec5c21bda4ed8b9b4c7426b0a202533ced4334d4

14899d1f285c504a29d913e9b85da269988e0231ff5f232acef1ef9e337a9d42

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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