Which versions of zwxbccaba are malicious?

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

How do I remediate zwxbccaba if I installed it?

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

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

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

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

Malicious package

zwxbccabaRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9926

Immediate action

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

gem uninstall zwxbccaba

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6e9cf117ac5c41601575f588c0bfd2276aaca53c791c3489659f81e425f1acc8

5ef7470a367804647ae6fb1ff17c1420af30c142c206891da196e988319fc1c9

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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