Malicious Code Injection in expensive_quelea_z3n Package - npm Vulnerability
Summary
MAL-2025-94376: Malicious code in expensive_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 expensive_quelea_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package was identified as part of a malicious campaign that aimed to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant security risks for users relying on this package.
Vulnerability Detail
The vulnerability stems from the malicious code embedded within the expensive_quelea_z3n package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are then continuously republished to the npm registry. The origin of this vulnerability is linked to a campaign that exploits the npm ecosystem, potentially leading to the proliferation of insecure packages and a compromised registry.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall expensive_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 remove the expensive_quelea_z3n package from your project by executing 'npm uninstall expensive_quelea_z3n'. This will prevent any malicious code from executing while you seek a secure alternative.
Conclusion
The expensive_quelea_z3n package poses a significant security risk due to its embedded malicious code. It is essential to take immediate action by updating or removing the package to safeguard your application. Utilizing tools like Vulert can help monitor for vulnerabilities in real-time and ensure your software remains secure.
See every vulnerability recorded for expensive_quelea_z3n →
FAQ
The malicious code is designed to modify package.json files, remove private flags, and generate random package names, which can lead to the pollution of 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 by this vulnerability without any signup.
Using this package can lead to security risks such as the introduction of insecure code, potential data breaches, and the compromise of your application's integrity.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and ensure to only use packages from trusted sources.
If immediate updates are not possible, consider removing the package and looking for secure alternatives while you assess the situation.
