Malicious Code Injection in upa-lubalalio-igsu Package

upa-lubalalio-igsu Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170083: Malicious code in upa-lubalalio-igsu (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 upa-lubalalio-igsu package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious payload embedded within the upa-lubalalio-igsu package. This payload 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 using this package, as it can lead to unauthorized access and manipulation of their projects.

How To Fix

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

npm uninstall upa-lubalalio-igsu

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 remove the upa-lubalalio-igsu package from your project by executing the command: npm uninstall upa-lubalalio-igsu. This will prevent any malicious code from executing while you seek a secure alternative.

Conclusion

The upa-lubalalio-igsu package has been identified as containing malicious code that poses a significant security risk. It is crucial for developers to take immediate action by updating or uninstalling the package to protect their projects from potential threats. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for upa-lubalalio-igsu →

Share this vulnerability

FAQ

The upa-lubalalio-igsu package is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation of derivative packages.

The malicious code can modify your package.json file, remove private flags, and create random package names, potentially leading to security vulnerabilities in your project.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

If you cannot update the package, consider uninstalling it as a temporary measure to prevent any malicious activity until a secure alternative is found.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest versions to minimize the risk of vulnerabilities.

How To Fix

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

npm uninstall upa-lubalalio-igsu

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