Malicious Code Injection in local_meadowlark_z3n Package
Summary
MAL-2025-87985: Malicious code in local_meadowlark_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 local_meadowlark_z3n package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods npm with derivative packages aimed at inflating developer reputation scores for token rewards. This package is particularly vulnerable due to its design, which allows for the automatic generation and publication of harmful variants.
Vulnerability Detail
The vulnerability in the local_meadowlark_z3n package stems from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This leads to the continuous republishing of these variants, which pollutes the npm registry and can compromise the integrity of projects that depend on this package. The malicious payload can potentially affect developers' reputations and the security of their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall local_meadowlark_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 avoid using the local_meadowlark_z3n package and replace it with an alternative package that provides similar functionality without the associated risks. Additionally, consider using the following command to uninstall the malicious package: npm uninstall local_meadowlark_z3n.
Conclusion
The local_meadowlark_z3n package has been identified as a vector for malicious code injection, posing significant risks to developers and their projects. It is essential to remove this package and monitor for any updates or patches. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for local_meadowlark_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of harmful derivative packages.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project and affecting your developer reputation.
You should uninstall the local_meadowlark_z3n package immediately and look for alternative packages that do not carry this risk.
Currently, there is no specific patch for the local_meadowlark_z3n package. The best course of action is to remove it from your project.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json. You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner.
