Malicious Code Injection in sure_python_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-96888: Malicious code in sure_python_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 'sure_python_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and sharing of reusable code. However, this package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that inflate developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in 'sure_python_z3n' arises from its association with the tea.xyz token reward campaign. The package contains scripts that automatically generate and publish derivative packages with randomized names, which can lead to the pollution of the npm registry. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, potentially compromising the integrity of the npm ecosystem and affecting developers relying on legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sure_python_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 'sure_python_z3n' package and replace it with a similar, trusted package that does not exhibit malicious behavior. Always verify the source and reputation of packages before including them in your project.
Conclusion
The 'sure_python_z3n' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant and proactive in managing their dependencies to safeguard their projects from such vulnerabilities.
See every vulnerability recorded for sure_python_z3n →
FAQ
The primary risk is that it can pollute the npm registry with malicious packages, potentially compromising the integrity of your project and affecting other developers.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application against this vulnerability using the Vulert playground without any signup.
If you have installed the package, it is recommended to uninstall it immediately and replace it with a trusted alternative.
The malicious code modifies the package.json file to remove private flags and generates random package names, which are then republished to inflate developer reputation scores.
Yes, you can prevent similar vulnerabilities by regularly auditing your dependencies, using trusted sources, and employing tools like Vulert to monitor for vulnerabilities.
