Which versions of uxlambcal1 are malicious?

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

How do I remediate uxlambcal1 if I installed it?

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

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

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

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

Malicious package

uxlambcal1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9065

Immediate action

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

gem uninstall uxlambcal1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8228b80c191b53784e76952e3af7a8d2e7cb58a7631680f24a663f7b79f9aa45

0133e2e3bc3a973b541e9863fa9c6de0ff9fbf424cd2021a1f09d4d437a56baa

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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