Which versions of xabczztest are malicious?

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

How do I remediate xabczztest if I installed it?

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

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

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

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

Malicious package

xabczztestRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9520

Immediate action

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

gem uninstall xabczztest

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5b0c09694cb67d88823b0e38e26e0944f1d6b0b4a8c419b5f7e39be86e30c9ac

4b4aeb42a14a677eafaa6840232783242a747ca61f80033ec0db15385ec3ff48

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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