Malicious Code Injection in lost_coyote_z3n: A Threat to npm Packages
Summary
MAL-2025-95316: Malicious code in lost_coyote_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 'lost_coyote_z3n' package is part of the npm ecosystem, primarily used for JavaScript development. It has been identified as part of a malicious campaign that floods the npm registry 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 'lost_coyote_z3n' originates from its association with the tea.xyz token reward campaign. It contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only affects the package itself but also contributes to the overall degradation of the npm registry by continuously republishing variants, 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 lost_coyote_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, you can avoid using the 'lost_coyote_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.
Conclusion
The 'lost_coyote_z3n' package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.
See every vulnerability recorded for lost_coyote_z3n →
FAQ
The 'lost_coyote_z3n' package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
This vulnerability can lead to the pollution of the npm registry, making it difficult to trust other packages and potentially introducing security risks into your project.
You should remove the 'lost_coyote_z3n' package from your project immediately and monitor for any updates or patches that may address this vulnerability.
Yes, Vulert allows you to monitor and alert for open-source vulnerabilities in your software using just the package-lock.json file. You can check if your application is affected by this vulnerability using the Vulert playground.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about known vulnerabilities in the packages you use.
