Malicious Code Injection in fair_worm_z3n: A Threat to npm Packages
Summary
MAL-2025-102502: Malicious code in fair_worm_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
The package fair_worm_z3n is part of a larger trend of malicious npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by creating numerous derivative packages with randomized names. Their primary function is to inflate developer reputation scores in exchange for token rewards, but they pose significant risks to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in fair_worm_z3n stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also compromises the security and trustworthiness of the packages within it. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes such malicious practices.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall fair_worm_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 prevent the installation of this malicious package by using npm's package-lock.json to monitor your dependencies. Additionally, consider using tools like Vulert to check for vulnerabilities in your project. You can access the Vulert playground at https://vulert.com/scanner to analyze your application without any signup.
Conclusion
The fair_worm_z3n package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at manipulating the registry. It is crucial for developers to be vigilant and remove such packages from their projects. Utilizing tools like Vulert can help in monitoring and identifying vulnerabilities effectively.
See every vulnerability recorded for fair_worm_z3n →
FAQ
fair_worm_z3n is an npm package that has been identified as malicious, designed to manipulate the npm registry for token rewards.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies, potentially introducing security risks.
You should remove the fair_worm_z3n package from your project and check for any other affected packages.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
