Malicious Code Injection in melodic_lynx_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-95438: Malicious code in melodic_lynx_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 melodic_lynx_z3n 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 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 pollution of the npm registry and compromise the integrity of the ecosystem.
Vulnerability Detail
The vulnerability in melodic_lynx_z3n stems from its association with the tea.xyz token reward campaign, which utilizes malicious scripts to manipulate package metadata. The payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only affects the affected package but also contributes to the overall degradation of the npm registry, making it difficult for developers to trust the packages they use.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall melodic_lynx_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 measure, avoid using the melodic_lynx_z3n package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your package dependencies to identify and remove any malicious packages.
Conclusion
The melodic_lynx_z3n package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can help maintain the integrity of their projects and the broader open-source community.
See every vulnerability recorded for melodic_lynx_z3n →
FAQ
melodic_lynx_z3n is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.
The malicious code can modify your package.json file, remove private flags, and publish derivative packages, leading to potential security risks and pollution of the npm registry.
You can use Vulert, which monitors 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 melodic_lynx_z3n, you should uninstall it immediately using the command 'npm uninstall melodic_lynx_z3n' and review your other dependencies for potential vulnerabilities.
Yes, tools like Vulert can help monitor your projects for open-source vulnerabilities by analyzing your package-lock.json file.
