Malicious Code Injection in npm Package 'mysterious_quelea_z3n'
Summary
MAL-2025-95574: Malicious code in mysterious_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 package 'mysterious_quelea_z3n' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and republish variants, thus polluting the npm registry.
Vulnerability Detail
The vulnerability originates from the package's design to include autopublish scripts that alter the package.json file by removing private flags and changing version numbers. This allows the package to continuously generate and republish variants with random names, which can lead to a significant pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly install these malicious packages, as well as damage to the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall mysterious_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 'mysterious_quelea_z3n' package from your project by executing the command: 'npm uninstall mysterious_quelea_z3n'. This will prevent any malicious code from executing until a fix is applied.
Conclusion
The 'mysterious_quelea_z3n' package poses a significant risk due to its malicious code that modifies project files and repopulates the npm registry with harmful variants. It is crucial to take immediate action by updating or uninstalling the package to safeguard your project.
See every vulnerability recorded for mysterious_quelea_z3n →
FAQ
It is an npm package that is part of a campaign to inflate developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the installation of malicious code that modifies your project's package.json and republish variants, potentially compromising your project's integrity.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Simply upload your package-lock.json file to check for vulnerabilities.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in your open-source packages.
As a temporary measure, uninstall the package to mitigate any risk until a patched version is available.
