Which versions of zswcal3 are malicious?

The following RubyGems versions of zswcal3 are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate zswcal3 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zswcal3 (version 0.0.1).

Malicious package

zswcal3RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zswcal3 (RubyGems)

MAL-2026-9799

Immediate action

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

gem uninstall zswcal3

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

083d2b9c52e4b0ef2098ec3f3254763fbfbb977200df11f7cb7f302c042b777b

37ba6bc98c3c3a8a2ab450f4447bb3cb3b5c97bd91692bedaf9dae0902fa1949

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04450RLUA-2026-10388

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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