Malicious Code Exploit in fresh_fox_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-94611: Malicious code in fresh_fox_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 fresh_fox_z3n is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate the npm registry and inflate developer reputation scores through the automatic generation of derivative packages.
Vulnerability Detail
The vulnerability in fresh_fox_z3n originates from its association with malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also poses a risk to developers who may unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall fresh_fox_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 fresh_fox_z3n package and any other packages associated with the tea.xyz token reward campaign. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The fresh_fox_z3n package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. It is essential for developers to remain vigilant, update their packages, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for fresh_fox_z3n →
FAQ
fresh_fox_z3n is an npm package that has been linked to malicious activities, specifically designed to manipulate the npm registry.
This vulnerability can compromise the integrity of your project by introducing malicious code that alters your package dependencies and potentially exposes your project to further attacks.
If you have installed fresh_fox_z3n, you should immediately update or remove the package to mitigate any risks associated with the vulnerability.
You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.
Yes, tools like Vulert can help identify vulnerabilities in your npm packages by analyzing your package-lock.json file.
