Malicious Code Injection in commitizen-playwright-selenium-publish Package
Summary
MAL-2025-186242: Malicious code in commitizen-playwright-selenium-publish (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 commitizen-playwright-selenium-publish package is part of the npm ecosystem, designed to facilitate automated testing and publishing of applications using Playwright and Selenium. However, it has been compromised, leading to significant security concerns due to the injection of malicious code that manipulates package metadata and floods the npm registry.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the commitizen-playwright-selenium-publish package. This payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are then published to the npm registry. This behavior not only compromises the integrity of the affected package but also contributes to the pollution of the npm ecosystem, potentially affecting other developers and their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall commitizen-playwright-selenium-publishIf 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, avoid using the commitizen-playwright-selenium-publish package until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The commitizen-playwright-selenium-publish package has been compromised, leading to significant security vulnerabilities that can affect developers and their applications. It is crucial to remove the package and monitor for updates or alternatives to ensure the security of your projects.
See every vulnerability recorded for commitizen-playwright-selenium-publish →
FAQ
The malicious code modifies package metadata and publishes numerous variants to the npm registry, which can lead to reputation inflation and ecosystem pollution.
You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.
If you have installed the package, immediately uninstall it using 'npm uninstall commitizen-playwright-selenium-publish' and check for any other dependencies that may be affected.
Yes, consider using other testing frameworks or publishing tools that do not have known vulnerabilities and are actively maintained.
Regularly check your dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time by analyzing your package-lock.json.
