Which versions of zswacal1 are malicious?

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

How do I remediate zswacal1 if I installed it?

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

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

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

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

Malicious package

zswacal1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

zswacal1 is a confirmed malicious RubyGems package (MAL-2026-9794) 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 zswacal1 (RubyGems)

MAL-2026-9794

Immediate action

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

gem uninstall zswacal1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5fe586f131fb09bcfd81878cab8a62d91653b58f7a442e37ff1621db2d7db015

5284a4521d13b72103aaaa732de18e924f055d63d300d2d9c8dc40d0b3d11f80

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for zswacal1 (version 0.0.1).
If you installed it — respond
Remove zswacal1 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 zswacal1 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. zswacal1 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-04445RLUA-2026-10383

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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