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

upa-lukzuli-ilu Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170118: Malicious code in upa-lukzuli-ilu (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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package 'upa-lukzuli-ilu' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'upa-lukzuli-ilu' originates from its involvement in a malicious campaign that utilizes autopublish scripts to generate and publish derivative packages with randomized names. This manipulation alters the package.json file by removing private flags, changing version numbers, and continuously republishing variants, which can lead to pollution of the npm registry and compromise the security of dependent applications.

How To Fix

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

npm uninstall upa-lukzuli-ilu

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 lock your dependencies to a specific version that does not include 'upa-lukzuli-ilu'. This can be done by modifying your package.json file to exclude this package and then running 'npm install' to update your node_modules.

Conclusion

The 'upa-lukzuli-ilu' package presents a significant security risk due to its malicious code designed to manipulate npm package metadata. It is essential to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities in real-time.

See every vulnerability recorded for upa-lukzuli-ilu →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package metadata and republish variants to inflate developer reputation scores.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.

You should uninstall the package immediately using 'npm uninstall upa-lukzuli-ilu' and review your dependencies for any other malicious packages.

There are no patches available for 'upa-lukzuli-ilu' as it is recommended to remove the package entirely from your project.

Vulert uses your package-lock.json to monitor and alert you in real-time for open-source vulnerabilities, ensuring your software remains secure.

How To Fix

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

npm uninstall upa-lukzuli-ilu

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