Malicious Code Injection in dizzy_catfish_z3n: npm Package Vulnerability
Summary
MAL-2025-94085: Malicious code in dizzy_catfish_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 'dizzy_catfish_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in 'dizzy_catfish_z3n' stems from its association with the tea.xyz token reward campaign. It includes malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dizzy_catfish_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 workaround, you can avoid using the 'dizzy_catfish_z3n' package altogether. If it is already in use, consider replacing it with a similar package that does not have known vulnerabilities.
Conclusion
The 'dizzy_catfish_z3n' package poses a significant risk due to its malicious code that manipulates package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their applications for vulnerabilities using tools like Vulert.
See every vulnerability recorded for dizzy_catfish_z3n →
FAQ
The main issue is that it contains malicious code that modifies package metadata and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
You should remove the package from your project and monitor for any updates or patches that may address the vulnerability.
Yes, consider using other reputable packages that provide similar functionality without the associated risks.
This vulnerability can lead to the pollution of the npm registry, making it difficult for developers to find trustworthy packages and potentially compromising the security of their applications.
