Malicious Code Injection in typical_flyingfish_z3n: A Threat to npm Packages
Summary
MAL-2025-97066: Malicious code in typical_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 typical_flyingfish_z3n is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. It is designed to generate and publish derivative packages with randomized names, aimed at inflating developer reputation scores for rewards. This package, like others in the campaign, contains scripts that automate the publication process, making it a significant threat to the integrity of the npm registry.
Vulnerability Detail
The vulnerability in typical_flyingfish_z3n stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the security and reliability of dependent projects. The origin of this issue is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms for malicious purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall typical_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 remove the typical_flyingfish_z3n package from your project by executing: npm uninstall typical_flyingfish_z3n. This will prevent any malicious code from executing while you seek a permanent fix.
Conclusion
The typical_flyingfish_z3n package poses a significant risk due to its malicious code that alters package metadata and republishing behavior. It is crucial for developers to take immediate action by updating or removing the package to safeguard their projects from potential threats.
See every vulnerability recorded for typical_flyingfish_z3n →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, which aims to inflate developer reputation scores through automated publishing.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project and introducing security risks.
You should update the package to a patched version if available or remove it from your project to avoid the associated risks.
You can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
