Which versions of zwcalx0 are malicious?

The following RubyGems versions of zwcalx0 are flagged malicious: 0.0.483. Treat any of these as compromised.

How do I remediate zwcalx0 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwcalx0 (version 0.0.483).

Malicious package

zwcalx0RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zwcalx0 (RubyGems)

MAL-2026-9839

Immediate action

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

gem uninstall zwcalx0

Malicious versions

1 flagged

0.0.483

Indicators of compromise (SHA-256)

2234055b499764c181d21c96f2b901819de770eaefbeb709fd16a8f778ad8fb2

72c06b331c61a18fad0244b396b00526f00169610c57146c013aec13e760be64

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04490RLUA-2026-10428

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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