Which versions of uxwcookie1 are malicious?

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

How do I remediate uxwcookie1 if I installed it?

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

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

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

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

Malicious package

uxwcookie1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9069

Immediate action

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

gem uninstall uxwcookie1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7f90841bbb5ea7eac11ab05c8d38c1eb9de714511bc8edb5a0a838030be33340

14c545ac6f6faa034d621145e6d66831925598b4b0e7c29d124d9fe8ef20ebd5

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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