Malicious Code Injection in alternative_fly_z3n Package
Summary
MAL-2025-98615: Malicious code in alternative_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 alternative_fly_z3n package is part of the npm ecosystem, typically used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to inflate developer reputation scores through automated scripts that publish numerous variants of itself, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in the alternative_fly_z3n package stems from its association with the tea.xyz token reward campaign. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which allows it to continuously republish itself and other variants. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these tainted packages, potentially leading to security breaches and loss of trust in the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall alternative_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 avoid using the alternative_fly_z3n package and any packages that depend on it. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The alternative_fly_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 monitor for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for alternative_fly_z3n →
FAQ
The alternative_fly_z3n package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
The vulnerability can lead to the inclusion of malicious code in your project, compromising its security and potentially affecting your application's integrity.
If you have installed the alternative_fly_z3n package, you should uninstall it immediately using the command npm uninstall alternative_fly_z3n.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. Visit https://vulert.com for more information.
While specific alternatives depend on your project's requirements, it is advisable to research and select well-maintained packages from reputable sources in the npm registry.
