Malicious Code Injection in bright_flyingfish_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-100103: Malicious code in bright_flyingfish_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 bright_flyingfish_z3n is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing numerous derivative packages with randomized names. This behavior poses a significant risk to the integrity of the npm registry and can lead to the proliferation of malicious code.
Vulnerability Detail
The vulnerability in bright_flyingfish_z3n originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, polluting the npm registry and potentially compromising other projects that depend on these packages. The malicious scripts included in the package are designed to automate this process, making it difficult for developers to identify and mitigate the threat.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall bright_flyingfish_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 avoid using the bright_flyingfish_z3n package and look for alternative packages that provide similar functionality without the associated risks. Ensure to audit your package-lock.json file for any other potentially malicious packages.
Conclusion
The bright_flyingfish_z3n package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package from their projects and to regularly audit their dependencies for vulnerabilities. Utilizing tools like Vulert can help in monitoring and ensuring the security of your applications.
See every vulnerability recorded for bright_flyingfish_z3n →
FAQ
bright_flyingfish_z3n is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.
You should uninstall the package immediately using the command: npm uninstall bright_flyingfish_z3n and audit your project for any other affected packages.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can also check your application against known vulnerabilities using the Vulert playground.
Yes, you should look for alternative packages that provide similar functionality without the associated risks. Always verify the reputation and security of packages before installation.
