Malicious Code Injection in puny_fish_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-96113: Malicious code in puny_fish_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
puny_fish_z3n is an npm package that appears to be part of a larger scheme involving the tea.xyz token reward campaign. This package is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names, which can inflate developer reputation scores. The malicious nature of this package poses a significant risk to developers and users relying on npm for package management.
Vulnerability Detail
The vulnerability in puny_fish_z3n originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This not only pollutes the npm registry but also compromises the integrity of the packages within it, potentially leading to security risks for applications that depend on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall puny_fish_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 puny_fish_z3n package from your project by executing the following command: npm uninstall puny_fish_z3n. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The puny_fish_z3n package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is crucial for developers to take immediate action by updating or uninstalling the package to protect their applications from potential security risks. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for puny_fish_z3n →
FAQ
puny_fish_z3n is an npm package that is part of a malicious campaign aimed at manipulating the npm registry.
The vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity.
You should uninstall the package immediately and monitor for any updates or patches that may be released.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
