Which versions of uxtestok are malicious?

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

How do I remediate uxtestok if I installed it?

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

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

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

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

Malicious package

uxtestokRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9067

Immediate action

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

gem uninstall uxtestok

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a14f95474800ba1ac83b6a6d1753fb1d96adc5d2c28f474fadb7540b52e0f4b2

5b5d61f5f5a8ef4d852c8387e098872a7a7867e6f092b425ebbe5211168c0317

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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