Which versions of zwtlist are malicious?

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

How do I remediate zwtlist if I installed it?

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

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

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

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

Malicious package

zwtlistRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9917

Immediate action

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

gem uninstall zwtlist

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2873fa6f26733d10bb67bfc8bc34a0bcfe8c3c3a972f6fd646dabe0c8ef77dd3

a2310b49f5dd27b17b74acdc2cca295e130a6a8841859f13759139626fcee6bf

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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