Which versions of zbzrjincf11b0 are malicious?

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

How do I remediate zbzrjincf11b0 if I installed it?

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

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

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

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

Malicious package

zbzrjincf11b0RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9562

Immediate action

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

gem uninstall zbzrjincf11b0

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

59aff083aa2812d99892d6ab2e8eb61a9cdac8e7bb4a56fe7c2df26f1d896d06

720be6ea28ccd0944ca9eebc06ee470225c0bad3f952ec1424d090b075b88ce6

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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