Malicious Code Vulnerability in damaged_flea_z3n Package
Summary
MAL-2025-101194: Malicious code in damaged_flea_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 damaged_flea_z3n package 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 package metadata and inflate developer reputation scores, making them a significant risk to developers and users alike.
Vulnerability Detail
The vulnerability in the damaged_flea_z3n package 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 to republish variants continuously. This behavior not only pollutes the npm registry but also poses a risk of unintentional dependency on malicious code, potentially leading to security breaches and data leaks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall damaged_flea_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 the damaged_flea_z3n package by using npm's package-lock.json file to lock dependencies. Ensure that your project does not include this package in its dependencies.
Conclusion
The damaged_flea_z3n package presents a significant security risk due to its malicious code that alters package metadata and repopulates the npm registry with harmful variants. It is crucial to remove this package from your projects and monitor for any updates or patches to ensure the security of your applications.
See every vulnerability recorded for damaged_flea_z3n →
FAQ
The damaged_flea_z3n package is an npm package associated with a token reward campaign that has been identified as malicious.
This vulnerability can lead to the introduction of malicious code into your project, potentially compromising security and stability.
You should remove the damaged_flea_z3n package from your project immediately and monitor for any updates or patches.
You can use tools like Vulert, which monitors your package-lock.json file 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 without signing up.
