Which versions of zwcalx2 are malicious?

The following RubyGems versions of zwcalx2 are flagged malicious: 0.0.486. Treat any of these as compromised.

How do I remediate zwcalx2 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwcalx2 (version 0.0.486).

Malicious package

zwcalx2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zwcalx2 (RubyGems)

MAL-2026-9845

Immediate action

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

gem uninstall zwcalx2

Malicious versions

1 flagged

0.0.486

Indicators of compromise (SHA-256)

e8ae698949b1ed1a2e48724493b25442ab91970d542369d1a0390014230b9a4b

f9119b8ff594780847dfc46a931263e49f70f91d4d357f8f740467dd521152ba

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04496RLUA-2026-10434

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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