Malicious Code Injection in lengthy_quelea_z3n Package
Summary
MAL-2025-95228: Malicious code in lengthy_quelea_z3n (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 lengthy_quelea_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards through various scripts that automate the publication of derivative packages. 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 package's malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores and pollute the npm registry with numerous derivative packages. The continuous republishing of these variants poses significant risks, including potential exposure of sensitive information and 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 lengthy_quelea_z3nIf 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 the lengthy_quelea_z3n package by adding it to your project's .npmrc file with the following line: 'package-lock=false'. This will help avoid the installation of this malicious package until a fix is implemented.
Conclusion
The lengthy_quelea_z3n package poses a significant security threat due to its malicious code that alters package configurations and floods the npm registry. It is essential to remove this package and monitor your project for any unauthorized changes. Utilizing tools like Vulert can help maintain the security of your open-source dependencies.
See every vulnerability recorded for lengthy_quelea_z3n →
FAQ
The primary risk is the modification of your package.json file, which can lead to the exposure of sensitive information and the proliferation of malicious packages in the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By utilizing the Vulert playground, you can check if your application is affected without any signup.
If you have installed the package, it is crucial to remove it immediately and check your project for any unauthorized changes made to your package.json file.
While specific exploits have not been detailed, the malicious behavior of the package can lead to significant security risks, including unauthorized access and data leakage.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from trusted sources.
