Malicious Code Injection in upa-lubali-ilualu Package - npm Vulnerability
Summary
MAL-2025-170106: Malicious code in upa-lubali-ilualu (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The upa-lubali-ilualu package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing system. It is designed to generate and publish derivative packages with randomized names, ultimately inflating developer reputation scores for token rewards in the tea.xyz protocol. The malicious behavior of this package poses significant risks to developers and the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the upa-lubali-ilualu package, which contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the security of applications that rely on these packages. The malicious code can affect any project that inadvertently includes this package, leading to reputational damage and security risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall upa-lubali-ilualuIf 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 prevent the installation of this package by using npm's package-lock.json file to monitor dependencies. Ensure that your project does not include upa-lubali-ilualu or any of its variants. You can also use tools like Vulert to monitor your project for vulnerabilities without needing to access the code directly.
Conclusion
The upa-lubali-ilualu package poses a significant threat to the npm ecosystem due to its malicious behavior. Developers must take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help ensure ongoing security and integrity in your applications.
See every vulnerability recorded for upa-lubali-ilualu →
FAQ
The upa-lubali-ilualu package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
This vulnerability can lead to the pollution of the npm registry and may compromise the security of your project if it inadvertently includes this package.
Remove the upa-lubali-ilualu package from your project and review your package-lock.json file to ensure no malicious packages are included.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time without requiring access to the code.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
