Which versions of zwtd103 are malicious?

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

How do I remediate zwtd103 if I installed it?

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

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

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

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

Malicious package

zwtd103RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9903

Immediate action

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

gem uninstall zwtd103

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9e9b528a49f8687180faddc004dfa6792aef3974ce56e9e51433449f837dd094

5c3b399a04cf6b975ee4813ed777a0296806f05b373a255d6a3a9acde041b751

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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