Which versions of uxjanlamb3 are malicious?

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

How do I remediate uxjanlamb3 if I installed it?

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

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

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

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

Malicious package

uxjanlamb3RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9059

Immediate action

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

gem uninstall uxjanlamb3

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

29295c57e04d72b538182632d8f6f6e5543f568230ba2179881b5c53972b95f4

99db616c564a63cd472612761ebcd7ef562bca5d229b3494a1e722e57a6223c8

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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