Malicious Code Detected in cherry-e6o-project Package

cherry-e6o-project Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16913: Malicious code in cherry-e6o-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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The cherry-e6o-project is an npm package designed for specific functionalities within JavaScript applications. It is utilized by developers for various tasks, but it has been identified as containing malicious code that poses a significant risk to users and their applications. This vulnerability can lead to unauthorized access, data breaches, or other malicious activities.

Vulnerability Detail

The vulnerability in the cherry-e6o-project package stems from the inclusion of malicious code that was intentionally introduced. This code can compromise the security of applications that depend on this package, potentially leading to data theft, unauthorized operations, or system instability. The issue was first introduced in version 0 and affects all subsequent versions.

How To Fix

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

npm uninstall cherry-e6o-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 avoid using the cherry-e6o-project package in your application until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The cherry-e6o-project package has been identified as containing malicious code that poses significant risks to users. It is crucial to remove this package from your applications and monitor for updates or alternative solutions. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your dependencies.

See every vulnerability recorded for cherry-e6o-project →

Share this vulnerability

FAQ

The cherry-e6o-project is an npm package used in JavaScript applications, but it has been found to contain malicious code.

The malicious code was introduced intentionally by the package maintainers, affecting all versions from the start.

Using this package can lead to unauthorized access, data breaches, and other security issues in your application.

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

Remove the cherry-e6o-project package from your project and look for alternative packages or wait for a patched version.

How To Fix

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

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