Which versions of uxwcookie2 are malicious?

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

How do I remediate uxwcookie2 if I installed it?

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

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

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

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

Malicious package

uxwcookie2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9070

Immediate action

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

gem uninstall uxwcookie2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f21e8afd2dc4b1473094386bdfebd6cfc22439b731b277cf4c4e5593eac882b4

a9ac71b6af3886d12ccd721c5d639d155fa873b75083fd9b29b8abd85d8d2851

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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