Which versions of zzjinavcsbzr are malicious?

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

How do I remediate zzjinavcsbzr if I installed it?

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

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

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

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

Malicious package

zzjinavcsbzrRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9950

Immediate action

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

gem uninstall zzjinavcsbzr

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

adc31fec0c777f1c7080bab8c7105f8916af85e2b5f5eac66815bb342f4f9303

d9b3f82350e6079c9d31207530ffa4e2a0fbb0441645cbf2cb63263a1b836c8f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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