Which versions of zwtd102 are malicious?

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

How do I remediate zwtd102 if I installed it?

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

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

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

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

Malicious package

zwtd102RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9902

Immediate action

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

gem uninstall zwtd102

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f01a1a047f08bf760eda9376fafc20a353dcd89d8ac68e007cc663e60c2d7aa9

b267020b9b09ac284c58320a9afb17d361c037800abb9cefdbbba2ca4cd0e858

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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