Malicious Code Injection in chronic_koi_z3n Package: A Threat to npm Users
Summary
MAL-2025-100407: Malicious code in chronic_koi_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 chronic_koi_z3n package is part of the npm ecosystem, primarily used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious packages flooding the npm registry. This package, like others in the campaign, is designed to manipulate package metadata and inflate developer reputation scores through automated publishing scripts.
Vulnerability Detail
The vulnerability in the chronic_koi_z3n package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The origin of this vulnerability is tied to the tea.xyz token reward campaign, which aims to exploit npm's publishing system for fraudulent gains. The ramifications include potential pollution of the npm registry, increased risk of dependency confusion, and compromised developer reputations.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall chronic_koi_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 workaround, you can prevent the installation of this package by using npm's package-lock.json to monitor dependencies. If you are using Vulert, you can check your application for vulnerabilities without any installation. Use the following command to remove the package: npm uninstall chronic_koi_z3n.
Conclusion
The chronic_koi_z3n package poses a significant risk due to its malicious code that alters package metadata and exploits the npm registry. It is essential for developers to be vigilant and remove this package from their projects. Utilizing tools like Vulert can help monitor for such vulnerabilities effectively.
See every vulnerability recorded for chronic_koi_z3n →
FAQ
The chronic_koi_z3n package is an npm package associated with the tea.xyz token reward campaign, which has been identified as malicious.
The malicious code modifies your package.json file, potentially leading to unauthorized republishing of your packages and pollution of the npm registry.
You should uninstall the chronic_koi_z3n package immediately to prevent any potential risks to your project.
Yes, you can use tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time without needing to install additional software.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
