Which versions of zwtestabc2 are malicious?

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

How do I remediate zwtestabc2 if I installed it?

zwtestabc2 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed zwtestabc2 — how do I know if it already compromised me?

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

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

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

Malicious package

zwtestabc2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

zwtestabc2 is a confirmed malicious RubyGems package (MAL-2026-9911) that opens a backdoor for remote access (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in zwtestabc2 (RubyGems)

MAL-2026-9911

Immediate action

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

gem uninstall zwtestabc2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c894c2755ded8f859d6cfc30306f56a56f0f750c8d1b08fa373b56d57a8d4e61

136cf83f48bbc6d8df626f4b1dba83fc3322520ac1472d32258997c13687adff

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for zwtestabc2 (version 0.0.1).
If you installed it — respond
zwtestabc2 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If zwtestabc2 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. zwtestabc2 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-04562RLUA-2026-10500

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks zwtestabc2-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database