Which versions of zwcalx10 are malicious?

The following RubyGems versions of zwcalx10 are flagged malicious: 0.0.495. Treat any of these as compromised.

How do I remediate zwcalx10 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwcalx10 (version 0.0.495).

Malicious package

zwcalx10RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zwcalx10 (RubyGems)

MAL-2026-9841

Immediate action

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

gem uninstall zwcalx10

Malicious versions

1 flagged

0.0.495

Indicators of compromise (SHA-256)

75d83e85672b99de1af876848133959c11b1be0380e9e3c704ee7e7052e9c64f

22ca49209b401ef7e28aeaa417e0bf25aa592220311ea6623391471106703420

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04492RLUA-2026-10430

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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