Malicious Code Injection in commitizen-eclipse-sadr-chariklo Package

Summary

13/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-186240: Malicious code in commitizen-eclipse-sadr-chariklo (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The commitizen-eclipse-sadr-chariklo package is part of the npm ecosystem, primarily used for managing and automating the process of versioning and changelog generation in projects. It is designed to streamline the development workflow by providing a standardized way to commit messages and release versions. However, this package has been compromised, making it susceptible to malicious activities that can affect developers and their projects.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the commitizen-eclipse-sadr-chariklo package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. It is part of a broader scheme associated with the tea.xyz token reward campaign, which aims to inflate developer reputation scores by flooding the npm registry with derivative packages. The ramifications include potential pollution of the npm registry, unauthorized access to sensitive information, and disruption of the development workflow.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall commitizen-eclipse-sadr-chariklo

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 prevent the malicious code from executing by removing the commitizen-eclipse-sadr-chariklo package from your project. Use the following command to uninstall it: npm uninstall commitizen-eclipse-sadr-chariklo.

Conclusion

The commitizen-eclipse-sadr-chariklo package has been identified as containing malicious code that poses significant risks to developers and their projects. It is essential to take immediate action by updating or removing the package to safeguard your development environment. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for commitizen-eclipse-sadr-chariklo →

Share this vulnerability

FAQ

The vulnerability involves malicious code that alters package.json files and floods the npm registry with unauthorized packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application using the Vulert playground at Vulert Scanner.

Using the compromised package can lead to unauthorized access to your project's dependencies, pollution of the npm registry, and disruption of your development process.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and ensure that you only install packages from trusted sources.

If a patched version is not available, consider removing the package and exploring alternative packages that provide similar functionality without the security risks.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall commitizen-eclipse-sadr-chariklo

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback