Which versions of zwtestabc4 are malicious?

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

How do I remediate zwtestabc4 if I installed it?

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

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

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

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

Malicious package

zwtestabc4RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9913

Immediate action

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

gem uninstall zwtestabc4

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

187e28fb5ccd60e53dc1208ed92ff8f0330554271f8f4a222d3cdb8110aa305a

b2a2626e2dc830415a46c15e907ece1e826559f665cf2816548d1e7c4152dbb0

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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