Which versions of zwta6000 are malicious?

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

How do I remediate zwta6000 if I installed it?

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

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

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

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

Malicious package

zwta6000RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9897

Immediate action

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

gem uninstall zwta6000

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6a8fee9e3a813dbe84efba231909eb6c4bc4198e369e0065594d5f1bfaf6e65a

6524fa0db62e1af42aabc3cf58150ae505049a638cc5896214803b8c12ba6468

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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