Malicious Code Injection in commitlint-chalk-eclipse-init Package
Summary
MAL-2025-186246: Malicious code in commitlint-chalk-eclipse-init (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 commitlint-chalk-eclipse-init package is part of the npm ecosystem, primarily used for linting commit messages in JavaScript projects. It helps developers maintain consistent commit message formats, which is crucial for project collaboration and version control. However, this package has been compromised, leading to significant security concerns.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded in the commitlint-chalk-eclipse-init package. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, thereby inflating developer reputation scores. This behavior can lead to the pollution of the npm registry and potential exploitation of developers using this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall commitlint-chalk-eclipse-initIf 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 an immediate workaround, you can remove the commitlint-chalk-eclipse-init package from your project until a secure version is available. You can do this by executing the following command: npm uninstall commitlint-chalk-eclipse-init.
Conclusion
The commitlint-chalk-eclipse-init package has been compromised, posing significant risks to developers and their projects. It is crucial to take immediate action by updating or removing the package to mitigate potential threats. Utilizing tools like Vulert can further enhance your security posture by providing real-time monitoring for vulnerabilities.
See every vulnerability recorded for commitlint-chalk-eclipse-init →
FAQ
The vulnerability involves malicious code that modifies package.json files and generates random package names, leading to npm registry pollution.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
You should update the package to its latest patched version or uninstall it until a secure version is released.
Using compromised packages can lead to security breaches, data leaks, and potential exploitation of your application by malicious actors.
Vulert uses package-lock.json to monitor for open-source vulnerabilities, providing real-time alerts to help developers maintain secure applications.
