Malicious Code Injection in fatal_constrictor_z3n Package
Summary
MAL-2025-102602: Malicious code in fatal_constrictor_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 fatal_constrictor_z3n package is part of the npm ecosystem and has been identified as a component of the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious code that alters package metadata.
Vulnerability Detail
The vulnerability in the fatal_constrictor_z3n package 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 integrity of other packages. The source of this vulnerability is linked to the broader issue of malicious packages flooding the npm ecosystem, specifically targeting developers involved in the tea protocol token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall fatal_constrictor_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 fatal_constrictor_z3n package from your project by executing the following command: npm uninstall fatal_constrictor_z3n. This will prevent any malicious activity associated with the package until a secure version is available.
Conclusion
The fatal_constrictor_z3n package poses a significant risk due to its malicious code that alters package metadata and pollutes the npm registry. It is crucial for developers to stay informed about such vulnerabilities and take appropriate actions, including updating or removing affected packages to maintain the integrity of their projects.
See every vulnerability recorded for fatal_constrictor_z3n →
FAQ
fatal_constrictor_z3n is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project and exposing it to further malicious activities.
You should check the npm registry for any patched versions of the fatal_constrictor_z3n package. If available, updating to the latest version is recommended.
You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.
If immediate updates are not possible, consider uninstalling the package as a temporary measure to mitigate risks associated with the vulnerability.
