Malicious Code Injection in left_perch_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-95208: Malicious code in left_perch_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 left_perch_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security risks for developers and their applications.
Vulnerability Detail
The vulnerability in left_perch_z3n originates from its association with the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. The malicious code within this package modifies the package.json file to remove private flags, alters version numbers, and generates random package names to inflate developer reputation scores. This behavior not only compromises the integrity of the affected package but also pollutes 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 left_perch_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 left_perch_z3n package until a secure version is released. Additionally, you can monitor your package-lock.json file for any unauthorized changes, ensuring that no malicious code is introduced into your application.
Conclusion
The left_perch_z3n package poses a significant security risk due to its malicious code that alters package configurations and pollutes the npm registry. It is crucial for developers to remain vigilant, update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for left_perch_z3n →
FAQ
left_perch_z3n is an npm package that is part of a malicious campaign aimed at exploiting the npm registry.
The malicious code can compromise your application's integrity by modifying package configurations and introducing potentially harmful dependencies.
If you have installed left_perch_z3n, it is recommended to remove it from your project and monitor for any unauthorized changes in your package-lock.json file.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application for this vulnerability using the Vulert playground at Vulert Scanner without any signup.
To prevent future vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and ensure that you only install packages from trusted sources.
