Malicious Code Injection in critical_fox_z3n Package
Summary
MAL-2025-101080: Malicious code in critical_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 critical_fox_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the critical_fox_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 exposing users to further security risks. The package is part of a broader trend of malicious npm packages that exploit the registry for fraudulent purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall critical_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 remove the critical_fox_z3n package from your project by executing the command: 'npm uninstall critical_fox_z3n'. This will prevent any malicious code from executing in your environment until a secure version is available.
Conclusion
The critical_fox_z3n package has been identified as containing malicious code that poses a significant risk to users and the npm ecosystem. It is crucial to take immediate action to remove the package and monitor for any updates or patches. Utilizing tools like Vulert can help maintain the security of your open-source dependencies.
See every vulnerability recorded for critical_fox_z3n →
FAQ
The critical_fox_z3n package is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.
The vulnerability can lead to the modification of your package.json file, removal of private flags, and the generation of random package names, potentially compromising your application's integrity.
You should uninstall the critical_fox_z3n package immediately and check for any updates or patches that may address the vulnerability.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check your application against known vulnerabilities using the Vulert playground.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
