Malicious Code Injection in tight_kite_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-97015: Malicious code in tight_kite_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
tight_kite_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package, like others in the tea.xyz token reward scheme, is designed to manipulate the npm ecosystem by generating and publishing derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards, making it a significant threat to the integrity of the npm registry.
Vulnerability Detail
The vulnerability in tight_kite_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 applications that depend on these packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which aims to exploit the npm ecosystem for fraudulent gains.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tight_kite_z3n
If 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 tight_kite_z3n package and replace it with a trusted alternative. Always verify the integrity and source of packages before including them in your project.
Conclusion
The tight_kite_z3n package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at manipulating the registry. It is essential for developers to be vigilant, remove any affected packages, and utilize tools like Vulert to monitor their dependencies for vulnerabilities.
See every vulnerability recorded for tight_kite_z3n →
FAQ
tight_kite_z3n is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the security and reliability of applications that depend on affected packages.
You should uninstall the package immediately using 'npm uninstall tight_kite_z3n' and check for any other affected packages.
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.