Malicious Code Detected in cherry-ch2-project Package

cherry-ch2-project Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16906: Malicious code in cherry-ch2-project (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The cherry-ch2-project package is an npm library designed for developers to facilitate certain functionalities in their applications. It is commonly used for its ease of integration and user-friendly features. However, this package has been identified to contain malicious code, posing significant risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the cherry-ch2-project package originates from the inclusion of malicious code that can compromise the security of applications using this package. This code may lead to unauthorized access, data breaches, or other harmful effects on the system. The malicious nature of this vulnerability makes it critical for developers to address it immediately to safeguard their applications.

How To Fix

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

npm uninstall cherry-ch2-project

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, consider removing the cherry-ch2-project package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall cherry-ch2-project'. This will help prevent any potential exploitation of the vulnerability.

Conclusion

The cherry-ch2-project package has been identified to contain malicious code, which poses significant risks to applications using it. Developers are urged to update or uninstall the package to protect their systems. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for cherry-ch2-project →

Share this vulnerability

FAQ

The cherry-ch2-project package is an npm library used by developers to enhance their applications with specific functionalities.

The malicious code can lead to unauthorized access and potential data breaches, posing serious security risks.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

Yes, updating the cherry-ch2-project package to the latest version will help mitigate the risks associated with the malicious code.

As a temporary measure, consider uninstalling the cherry-ch2-project package from your project to prevent exploitation of the vulnerability.

How To Fix

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

npm uninstall cherry-ch2-project

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