Which versions of uxjinalamb2 are malicious?

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

How do I remediate uxjinalamb2 if I installed it?

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

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

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

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

Malicious package

uxjinalamb2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9062

Immediate action

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

gem uninstall uxjinalamb2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2a9bec5d78296e571c8e0e3395cf5f553fcc89bd09664ec3c5ba5fc2aaf422e3

f85605f76d589e544105cf0496f460c05c74007fec279261b516b28a5af86a88

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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