Which versions of zwcalx11 are malicious?

The following RubyGems versions of zwcalx11 are flagged malicious: 0.0.497. Treat any of these as compromised.

How do I remediate zwcalx11 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwcalx11 (version 0.0.497).

Malicious package

zwcalx11RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

zwcalx11 is a confirmed malicious RubyGems package (MAL-2026-9842) that executes malicious code on install (malicious version 0.0.497). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in zwcalx11 (RubyGems)

MAL-2026-9842

Immediate action

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

gem uninstall zwcalx11

Malicious versions

1 flagged

0.0.497

Indicators of compromise (SHA-256)

bcfa9ad58c5348d2210f08352bcff15005e9c03ce9a1cf2c2e999172a0ad8d01

6af076f1a663018f51bc47968020162b88c9544d9790023c668517fec5c996f5

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for zwcalx11 (version 0.0.497).
If you installed it — respond
Remove zwcalx11 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 zwcalx11 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. zwcalx11 on RubyGems has been identified as a malicious package (version 0.0.497 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04493RLUA-2026-10431

References

Credits

ReversingLabs · finder

Detect & block this

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