Which versions of uxjanlamb2 are malicious?

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

How do I remediate uxjanlamb2 if I installed it?

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

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

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

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

Malicious package

uxjanlamb2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9058

Immediate action

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

gem uninstall uxjanlamb2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8197e8448efdc4d701309a87b175b07285e48d14823fded99c0afd0bfead6c57

564af740de236e0ec01f86904cb43663ff05e43524c7cb128bce616626656c49

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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