Malicious Code Injection in upa-lukzuli-ilazou: A Threat to npm Packages

upa-lukzuli-ilazou Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170117: Malicious code in upa-lukzuli-ilazou (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package 'upa-lukzuli-ilazou' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is implicated in a malicious campaign associated with the tea.xyz token reward initiative. It is designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names, thus compromising the integrity of the npm registry.

Vulnerability Detail

The vulnerability stems from the malicious code embedded within the 'upa-lukzuli-ilazou' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include potential security risks for developers who unknowingly use these compromised packages, as well as the degradation of the npm ecosystem's reliability.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall upa-lukzuli-ilazou

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, you can avoid using the 'upa-lukzuli-ilazou' package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity of packages before installation.

Conclusion

The 'upa-lukzuli-ilazou' package poses a significant threat due to its malicious code designed to manipulate the npm registry. Developers should take immediate action to remove this package and consider alternatives to safeguard their projects from potential risks.

See every vulnerability recorded for upa-lukzuli-ilazou →

Share this vulnerability

FAQ

It is an npm package involved in a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.

You can use tools like Vulert to monitor your package-lock.json for vulnerabilities. Visit Vulert Scanner to check your application without any signup.

Using compromised packages can lead to security vulnerabilities, data breaches, and a loss of trust in the npm ecosystem.

No patch is available for the 'upa-lukzuli-ilazou' package; the best course of action is to uninstall it and seek alternatives.

Regularly audit your dependencies, use trusted sources, and leverage tools like Vulert to stay informed about vulnerabilities.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall upa-lukzuli-ilazou

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback