Which versions of zwxbclic are malicious?

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

How do I remediate zwxbclic if I installed it?

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

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

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

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

Malicious package

zwxbclicRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9930

Immediate action

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

gem uninstall zwxbclic

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5cfbd9039d9c6a7838ada0765e5966be56409a0d0757ccbbcda8303aebb39a6b

692dfc5e0e41055f588b79a02740eb3a2f3ae59079addb56abe75accadcd8b0e

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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