Which versions of zwxbccalag are malicious?

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

How do I remediate zwxbccalag if I installed it?

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

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

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

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

Malicious package

zwxbccalagRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9927

Immediate action

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

gem uninstall zwxbccalag

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

49fc5f18905d141e81bf449cf91a81c4698d50233f9d46f025ce8cd7d88fce57

acc16027da1bfdf59e1241e618cf7fe71b817b1234686d7430628a9d1d2d5425

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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