Which versions of zwan_cal_https are malicious?

The following RubyGems versions of zwan_cal_https are flagged malicious: 0.0.134. Treat any of these as compromised.

How do I remediate zwan_cal_https if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwan_cal_https (version 0.0.134).

Malicious package

zwan_cal_httpsRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zwan_cal_https (RubyGems)

MAL-2026-9836

Immediate action

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

gem uninstall zwan_cal_https

Malicious versions

1 flagged

0.0.134

Indicators of compromise (SHA-256)

f5d214494b8e5ca12224b3c5abe26321fb3a9c18ddd57f443b1f50bef8652cfd

3722107779266dbd43b3292600601ade5c2c8d66a85e24ac537ccbde5ae9dcbc

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04487RLUA-2026-10425

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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