Which versions of uxlambcal2 are malicious?

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

How do I remediate uxlambcal2 if I installed it?

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

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

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

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

Malicious package

uxlambcal2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9066

Immediate action

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

gem uninstall uxlambcal2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

63a82963aac20b1bbc0b7b82620a8f06b0269bbc9e5aa1a8fb98f4671a671588

cd0cfb10d12c4b8fc9a6042b16ed9f676f683ec9e8d2adc338e3c39b24a98c55

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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