Malicious Code Injection in miserable_fox_z3n: A Threat to npm Packages
Summary
MAL-2025-95498: Malicious code in miserable_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
miserable_fox_z3n is an npm package that appears to be part of a larger scheme involving the tea.xyz token reward campaign. This package, like many others in this campaign, is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names. Its functionality is compromised by malicious scripts that aim to inflate developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in miserable_fox_z3n stems from its inclusion in a malicious campaign that modifies package.json files to remove private flags and change version numbers. This allows the package to generate random names and continuously republish variants, ultimately polluting the npm registry. The malicious payload can lead to security risks for developers and users by introducing untrusted code into their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall miserable_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 miserable_fox_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any unauthorized changes to package.json files.
Conclusion
The miserable_fox_z3n package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is essential for developers to remove this package from their projects and monitor for any unauthorized changes. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities in the future.
See every vulnerability recorded for miserable_fox_z3n →
FAQ
The main issue is that it contains malicious code that modifies package.json files, allowing it to republish variants and pollute the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
You should uninstall the package immediately using the command: npm uninstall miserable_fox_z3n and check for any other affected packages.
Yes, using this package can lead to security risks, including the introduction of untrusted code into your projects and potential reputation damage.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about known vulnerabilities in the packages you use.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
