Malicious Code Injection in potential_leopon_z3n Package
Summary
MAL-2025-95954: Malicious code in potential_leopon_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 potential_leopon_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package, like many others in the campaign, is designed to manipulate npm's publishing system by generating and publishing derivative packages with randomized names. It aims to inflate developer reputation scores for token rewards, making it a target for malicious exploitation.
Vulnerability Detail
The vulnerability in the potential_leopon_z3n package originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious code can also affect developers' reputation scores and lead to unintended consequences in their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall potential_leopon_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 remove the potential_leopon_z3n package from your project by executing the following command: npm uninstall potential_leopon_z3n. This will prevent any malicious code from executing in your environment until a fix is available.
Conclusion
The potential_leopon_z3n package contains a significant vulnerability that can compromise your project's integrity and developer reputation. It is crucial to take immediate action by updating or removing the package and to continuously monitor your dependencies for vulnerabilities.
See every vulnerability recorded for potential_leopon_z3n →
FAQ
The potential_leopon_z3n package is an npm package associated with the tea.xyz token reward campaign, designed to manipulate npm's publishing system.
The vulnerability can lead to the modification of your package.json file, removal of private flags, and the generation of random package names, which can compromise your project's integrity.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can check your application for vulnerabilities without any signup at the Vulert playground.
If a patched version is not available, it is recommended to uninstall the package from your project to mitigate the risk of exploitation.
Regularly update your dependencies, monitor for vulnerabilities using tools like Vulert, and review your package.json for any suspicious packages.
