Malicious Code Injection in astro-ganymede-commitizen-cypress Package
Summary
MAL-2025-139604: Malicious code in astro-ganymede-commitizen-cypress (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 astro-ganymede-commitizen-cypress package is part of the npm ecosystem, designed to facilitate the use of Commitizen for managing commit messages. However, it has been identified as part of a malicious campaign that exploits npm's package management system. This package is vulnerable to a specific issue where it can be manipulated to publish unauthorized and harmful derivatives, affecting the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the package being associated with the tea.xyz token reward campaign, which floods npm with malicious packages. These packages contain scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the security of dependent applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall astro-ganymede-commitizen-cypressIf 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, consider removing the astro-ganymede-commitizen-cypress package from your project until a secure version is available. You can do this by executing: npm uninstall astro-ganymede-commitizen-cypress.
Conclusion
The astro-ganymede-commitizen-cypress package has been identified as containing malicious code that can compromise the integrity of the npm registry. It is crucial for developers to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities in their applications.
See every vulnerability recorded for astro-ganymede-commitizen-cypress →
FAQ
The malicious code modifies the package.json file to remove private flags and changes version numbers, allowing unauthorized republishing of the package.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
Using this package can lead to the pollution of the npm registry, potential security breaches, and compromised application integrity.
Regularly update your dependencies, use tools like Vulert for monitoring vulnerabilities, and audit your package-lock.json file for any suspicious packages.
Immediately uninstall the package and check for any updates or patches. Consider using Vulert to monitor your project for vulnerabilities.
