Critical Malicious Code Vulnerability in cherry-pxx-project (npm)

cherry-pxx-project Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16938: Malicious code in cherry-pxx-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-pxx-project is an npm package designed for developers to integrate specific functionalities into their applications. It is widely used due to its ease of use and extensive documentation. However, it has been identified to contain malicious code, posing significant risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the cherry-pxx-project stems from the inclusion of malicious code that can compromise the security of applications using this package. This code can lead to unauthorized access, data breaches, and potential exploitation of the affected systems. The malicious nature of this vulnerability was discovered by Amazon Inspector, highlighting the importance of scrutinizing third-party packages for security risks.

How To Fix

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

npm uninstall cherry-pxx-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 measure, you can prevent the use of the cherry-pxx-project package by removing it from your dependencies and replacing it with a different package that offers similar functionality. For example, you can use the following command to uninstall it: npm uninstall cherry-pxx-project.

Conclusion

The cherry-pxx-project package has been identified as containing malicious code, posing significant security risks to applications that utilize it. It is essential to remove this package and replace it with a secure alternative to safeguard your application from potential threats.

See every vulnerability recorded for cherry-pxx-project →

Share this vulnerability

FAQ

The cherry-pxx-project is an npm package used for integrating specific functionalities into applications, but it has been found to contain malicious code.

The vulnerability was discovered by Amazon Inspector, which identified the presence of malicious code within the cherry-pxx-project package.

The risks include unauthorized access to sensitive data, potential data breaches, and exploitation of the affected systems.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner without any signup.

If a suitable replacement is not available, consider reaching out to the community for recommendations or reviewing the functionality you need to find alternative solutions.

How To Fix

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

npm uninstall cherry-pxx-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