Which versions of zwxbccab are malicious?

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

How do I remediate zwxbccab if I installed it?

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

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

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

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

Malicious package

zwxbccabRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9925

Immediate action

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

gem uninstall zwxbccab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8af7d9b11d636dcffd91c109f53ed0b4528d658476394da50c74c31bab16b3e1

ba0d4c48c0f6cef206550a5b895c41e32439c4b1a38a4a7d9e4a91b0bd7d781a

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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