Which versions of zwcalx5 are malicious?

The following RubyGems versions of zwcalx5 are flagged malicious: 0.0.489. Treat any of these as compromised.

How do I remediate zwcalx5 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwcalx5 (version 0.0.489).

Malicious package

zwcalx5RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zwcalx5 (RubyGems)

MAL-2026-9848

Immediate action

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

gem uninstall zwcalx5

Malicious versions

1 flagged

0.0.489

Indicators of compromise (SHA-256)

bbcb230c29ad266a479ce5b8ad2c5af1195b7f78cb8230385bbdf72c04ff81cb

97086e533943867c4394dc76cb39a13ba2f2b63791e1a3e6f99f7882f1e5b52d

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04499RLUA-2026-10437

References

Credits

ReversingLabs · finder

Detect & block this

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