Which versions of zwxbccali are malicious?

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

How do I remediate zwxbccali if I installed it?

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

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

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

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

Malicious package

zwxbccaliRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9928

Immediate action

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

gem uninstall zwxbccali

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1a1ac80951301c2683c1341bbdcdef94bf9feec64f48dcddd47bcfc4082bf1f9

38b37d74684b781e7566bb722ead85a08146425f85152c3817c5df56cddee509

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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