Which versions of zwcalx1 are malicious?

The following RubyGems versions of zwcalx1 are flagged malicious: 0.0.484. Treat any of these as compromised.

How do I remediate zwcalx1 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwcalx1 (version 0.0.484).

Malicious package

zwcalx1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zwcalx1 (RubyGems)

MAL-2026-9840

Immediate action

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

gem uninstall zwcalx1

Malicious versions

1 flagged

0.0.484

Indicators of compromise (SHA-256)

b7692b807cfb5ae6e39053088c7d2fd70629a17c67f8d390aaf27e9fd3b314f4

dd5b4d74593598e96a62004b5d43ae928349021ba0b5e80030ba85ccdb2b9a95

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04491RLUA-2026-10429

References

Credits

ReversingLabs · finder

Detect & block this

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