Which versions of uxhttpslamb1 are malicious?

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

How do I remediate uxhttpslamb1 if I installed it?

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

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

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

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

Malicious package

uxhttpslamb1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9055

Immediate action

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

gem uninstall uxhttpslamb1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b5778e349633407688a5fcd11cd9bebed2649dc28499f74aac6592d642fa397d

d2c8fed39923c6a7b15447b8092bcc7ad7817ddb42b282e709041d1445582aea

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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