Which versions of zwcalx9 are malicious?

The following RubyGems versions of zwcalx9 are flagged malicious: 0.0.494. Treat any of these as compromised.

How do I remediate zwcalx9 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwcalx9 (version 0.0.494).

Malicious package

zwcalx9RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zwcalx9 (RubyGems)

MAL-2026-9852

Immediate action

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

gem uninstall zwcalx9

Malicious versions

1 flagged

0.0.494

Indicators of compromise (SHA-256)

f3c27e52e0ef2520b1643ec794129a3c83dee3458d3b758724a2fea99a2c1958

5ac8efce632d8db197b06184517b9f51401546533dd98a0ef2f42aab4adac045

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04503RLUA-2026-10441

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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