Which versions of uxhttpswands1 are malicious?

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

How do I remediate uxhttpswands1 if I installed it?

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

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

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

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

Malicious package

uxhttpswands1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9056

Immediate action

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

gem uninstall uxhttpswands1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0f0d90c0b75d5b03002798f2b7448ea6e7d3febc50337fefcf7bf25c30db92f9

b9a18adcf657498bb2e8c18c02935f253d2947f3db13da8cc10de744a50bbdc3

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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