Malicious Code Injection in Powerful Clownfish Z3N Package
Summary
MAL-2025-89487: Malicious code in powerful_clownfish_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 'powerful_clownfish_z3n' package is part of the npm ecosystem, often used in JavaScript projects for various functionalities. However, it has recently been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in the 'powerful_clownfish_z3n' package originates from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only compromises the integrity of the package but also contributes to the degradation of the npm ecosystem by continuously republishing variants, making it difficult for developers to trust the packages they use.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall powerful_clownfish_z3n
If 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 'powerful_clownfish_z3n' package from your project by executing the command: 'npm uninstall powerful_clownfish_z3n'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The 'powerful_clownfish_z3n' package has been identified as a vector for malicious code that can compromise the integrity of the npm ecosystem. It is crucial for developers to remain vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can help safeguard their applications against such threats.
See every vulnerability recorded for powerful_clownfish_z3n →
FAQ
The malicious code can lead to the automatic generation of derivative packages, which pollutes the npm registry and can compromise the security of applications relying on these packages.
You can use Vulert to monitor your application for vulnerabilities. By analyzing your package-lock.json file, Vulert provides real-time alerts for any open-source vulnerabilities.
To prevent similar vulnerabilities, always verify the source and integrity of packages before adding them to your project. Regularly update your dependencies and use tools like Vulert for continuous monitoring.
If immediate updates are not possible, consider removing the package from your project as a temporary measure to mitigate risks until a secure version is available.
Detailed information about this vulnerability can be found in the vulnerability report on the GitHub repository for malicious packages or through security advisories related to npm.