Which versions of zwtestxabc are malicious?

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

How do I remediate zwtestxabc if I installed it?

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

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

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

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

Malicious package

zwtestxabcRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9914

Immediate action

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

gem uninstall zwtestxabc

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8c95f41928327f151bbd4a014261ba07c646c3e9999b10d9b07fd725351634b1

b9a7082120a7ce276aa56eade32a39f778740fa16de907fca488aab263b08bcc

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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