Malicious Code Injection in previous_goldfish_z3n Package - npm Vulnerability
Summary
MAL-2025-96006: Malicious code in previous_goldfish_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 previous_goldfish_z3n package 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 aimed at manipulating developer reputation scores through the tea.xyz token reward system. Its functionality is compromised, as it includes scripts that automatically generate and publish derivative packages with altered metadata, leading to potential abuse and pollution of the npm registry.
Vulnerability Detail
The vulnerability in the previous_goldfish_z3n package stems from the inclusion of malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which can lead to the proliferation of spammy packages in the npm registry. The origin of this vulnerability is linked to a campaign that aims to inflate developer reputation scores for token rewards, posing risks such as registry pollution and potential security threats to applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall previous_goldfish_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 previous_goldfish_z3n package from your project by executing the following command: npm uninstall previous_goldfish_z3n. This will prevent any malicious code from executing in your environment until a secure version is available.
Conclusion
The previous_goldfish_z3n package has been compromised with malicious code that poses significant risks to developers and their applications. It is crucial to take immediate action by updating or removing the package to safeguard your project from potential threats. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for previous_goldfish_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores.
The malicious code modifies your package.json file, potentially leading to the installation of spammy packages and security vulnerabilities.
You should uninstall the package immediately and check for any updates or patches that may address the vulnerability.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.
