Malicious Code Injection in various_lemur_z3n: A Threat to npm Packages
Summary
MAL-2025-110355: Malicious code in various_lemur_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 'various_lemur_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. This behavior poses a significant risk to the integrity of the npm registry and can lead to the proliferation of malicious code.
Vulnerability Detail
The vulnerability in 'various_lemur_z3n' originates from its involvement in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, polluting the npm registry and potentially compromising other packages. The malicious payload can lead to unauthorized access, data breaches, and a loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall various_lemur_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 'various_lemur_z3n' package and monitor your project for any signs of malicious activity. Regularly audit your dependencies using tools like npm audit to identify vulnerabilities.
Conclusion
The 'various_lemur_z3n' package poses a significant risk due to its malicious behavior aimed at inflating developer reputation scores. It is crucial to remove this package from your project and monitor for any signs of compromise. Utilizing tools like Vulert can help maintain the security of your open-source dependencies.
See every vulnerability recorded for various_lemur_z3n →
FAQ
It is an npm package associated with a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can lead to the proliferation of malicious code, unauthorized access, and potential data breaches.
You should uninstall the package immediately and monitor your project for any suspicious activity.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
Regularly audit your dependencies, keep your packages updated, and use tools like Vulert to monitor for vulnerabilities.
