Which versions of zwtcook2 are malicious?

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

How do I remediate zwtcook2 if I installed it?

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

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

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

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

Malicious package

zwtcook2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9899

Immediate action

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

gem uninstall zwtcook2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e4571acf7b26105ae8d097fce9e8af8cf84f90e8b4983997c5d072b93b4377db

60888b99a2da41061048d050b7d0d9ba33d11a9d582bfb63310e150260b9d852

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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