Which versions of uxbcrwands2 are malicious?

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

How do I remediate uxbcrwands2 if I installed it?

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

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

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

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

Malicious package

uxbcrwands2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9037

Immediate action

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

gem uninstall uxbcrwands2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2111a8bea39bfc0f071de93e435e0ac7584a1c25c8bc2e121350b918d3c3f96e

2735ed941f8b7cc3dcbce9e015db722ab961c6b0b5f0a5f2f920affcbda8d9c5

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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