Malicious Code Injection in laila-ubi80-breki: A Threat to npm Ecosystem
Summary
MAL-2025-74108: Malicious code in laila-ubi80-breki (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 package 'laila-ubi80-breki' 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 associated with the tea.xyz token reward initiative. The primary functionality of such packages is to manipulate npm's publishing system, leading to the proliferation of derivative packages that can compromise the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'laila-ubi80-breki' stems from its malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to inflate developer reputation scores fraudulently. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages in their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall laila-ubi80-brekiIf 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 'laila-ubi80-breki' package from your project by executing the command: 'npm uninstall laila-ubi80-breki'. This will prevent any malicious code from executing in your environment until a secure version is available.
Conclusion
The 'laila-ubi80-breki' package poses a serious threat to the npm ecosystem due to its malicious code that manipulates package metadata and floods the registry. It is essential to take immediate action by updating or removing the package to safeguard your projects. Utilizing tools like Vulert can enhance your ability to monitor and manage vulnerabilities effectively.
See every vulnerability recorded for laila-ubi80-breki →
FAQ
The primary threat is the injection of malicious code that alters package metadata and floods the npm registry with compromised packages.
You can use Vulert to monitor your application for vulnerabilities. Simply upload your package-lock.json file to the Vulert playground at Vulert Scanner to check for any affected packages.
If you have installed this package, it is recommended to uninstall it immediately and check for any updates or patches.
While specific exploits have not been detailed, the malicious behavior of the package can lead to significant security risks, including unauthorized access to your project.
Vulert provides real-time monitoring and alerts for open-source vulnerabilities using your package-lock.json file, allowing you to stay informed about potential threats.
