Which versions of zwtestabc1 are malicious?

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

How do I remediate zwtestabc1 if I installed it?

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

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

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

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

Malicious package

zwtestabc1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9910

Immediate action

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

gem uninstall zwtestabc1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

66510079b7b7d0a99467869a0cdff333f2bbe64986f7ac150463dc45937cf466

e4e6cccb44ed8377f3eb9f20dc65a20b6e509bc0f4de627a81409f66967b55be

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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