Malicious Code Injection in deep_fly_z3n: A Threat to npm Packages
Summary
MAL-2025-98670: Malicious code in deep_fly_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 'deep_fly_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign that has been linked to a series of malicious activities aimed at inflating developer reputation scores. This package, like others in the campaign, is designed to automatically generate and publish derivative packages with randomized names, posing a significant risk to the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'deep_fly_z3n' originates from its malicious design, which includes 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 security of the affected package but also pollutes the npm registry with numerous derivative packages, making it difficult for developers to identify legitimate packages. The ramifications include potential exploitation of the npm ecosystem and damage to developer reputations.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall deep_fly_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 prevent the installation of this malicious package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include 'deep_fly_z3n' in its dependencies. You can also use the following command to uninstall the package if it is already installed: npm uninstall deep_fly_z3n.
Conclusion
The 'deep_fly_z3n' package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities. Staying informed and proactive is key to maintaining the security of your applications.
See every vulnerability recorded for deep_fly_z3n →
FAQ
The vulnerability involves malicious code that modifies package.json files and publishes numerous derivative packages to inflate reputation scores.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By analyzing your package-lock.json, you can determine if your application is affected.
You should uninstall the package immediately using the command: npm uninstall deep_fly_z3n.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in real-time.
Detailed information can be found on the GitHub repository of malicious packages, specifically under the entry for deep_fly_z3n.
