Which versions of zwcalx6 are malicious?

The following RubyGems versions of zwcalx6 are flagged malicious: 0.0.490. Treat any of these as compromised.

How do I remediate zwcalx6 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwcalx6 (version 0.0.490).

Malicious package

zwcalx6RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zwcalx6 (RubyGems)

MAL-2026-9849

Immediate action

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

gem uninstall zwcalx6

Malicious versions

1 flagged

0.0.490

Indicators of compromise (SHA-256)

10b5ad16d8805c491fb73ddde1c5e73903c09bb08ddf8c0f8cf3ed514baee97b

36d1550fbc09cb8aa3a580e702a5768f1dbdaf67ec60c3399b57bed59af7a40a

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04500RLUA-2026-10438

References

Credits

ReversingLabs · finder

Detect & block this

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