Which versions of uxproject11 are malicious?

The following npm versions of uxproject11 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate uxproject11 if I installed it?

uxproject11 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed uxproject11 — how do I know if it already compromised me?

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

Yes — uxproject11 is associated with the GHSA-vvjv-x5r6-jrrr, RLMA-2026-01637 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 uxproject11 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for uxproject11 (version 1.0.0).

Malicious package

uxproject11npm

Advisory published Feb 25, 2026Updated Mar 19, 2026

uxproject11 is a confirmed malicious npm package (MAL-2026-1234) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in uxproject11 (npm)

MAL-2026-1234

Immediate action

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

npm uninstall uxproject11

What this malware does

Collects and exfiltrates sensitive system information to suspicious domains. Multiple YARA rules are triggered. High entropy file. Extension mismatch.

The package uxproject11 was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

8b478ab519bbd87949cad8be7d77296e0eddd01aa0be1b4b168ed2f6a0f74135

0868075a854e67d1b0488d3bf20ce740b22c937b7aa050b39598fc528d9e84a1

3e29b515ad479bbcf07939cc7f56c1edd353a0ade06b1f569b333ec43a7427d9

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for uxproject11 (version 1.0.0).
If you installed it — respond
uxproject11 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If uxproject11 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. uxproject11 on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-vvjv-x5r6-jrrrRLMA-2026-01637

References

Credits

Amazon Inspector · finder
ReversingLabs · finder
SafeDep · finder

Detect & block this

O3 blocks uxproject11-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database