Malicious Code Injection in traditional_lizard_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-97047: Malicious code in traditional_lizard_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 'traditional_lizard_z3n' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This behavior poses a significant risk to the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'traditional_lizard_z3n' originates from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of variants, polluting the npm registry and potentially leading to reputation damage for developers and security risks for users who unknowingly install these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall traditional_lizard_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 'traditional_lizard_z3n' package and instead look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and source of packages before installation.
Conclusion
The traditional_lizard_z3n package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package from their projects and adopt best practices for dependency management to safeguard their applications.
See every vulnerability recorded for traditional_lizard_z3n →
FAQ
The primary risk is the injection of malicious code that modifies package metadata and floods the npm registry with unwanted variants, potentially harming developer reputations.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By uploading your package-lock.json file, you can check for vulnerabilities without requiring installation.
If you have installed the package, you should uninstall it immediately using 'npm uninstall traditional_lizard_z3n' and review your project for any other potentially harmful packages.
Yes, you should look for reputable packages that offer similar functionality. Always check the package's documentation and community feedback before installation.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from trusted sources.
