Malicious Code Detected in ccxte Package - Immediate Action Required

ccxte Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16689: Malicious code in ccxte (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 ccxte package is an npm library designed to facilitate various functionalities within JavaScript applications. It is often utilized for its ease of integration and lightweight nature. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the ccxte package originates from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may lead to unauthorized access, data breaches, or other malicious activities within the affected systems. The presence of such vulnerabilities highlights the importance of scrutinizing third-party packages before integration.

How To Fix

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

npm uninstall ccxte

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 ccxte package from your project until a secure version is released. You can do this by executing the command: npm uninstall ccxte. This will help mitigate the risk of exposure to the malicious code.

Conclusion

The discovery of malicious code in the ccxte package underscores the critical need for vigilance when using third-party libraries. Immediate action is required to update or remove the package to safeguard your applications. Regular monitoring of dependencies is essential to maintain security.

See every vulnerability recorded for ccxte →

Share this vulnerability

FAQ

The ccxte package is an npm library used in JavaScript applications for various functionalities, but it has been found to contain malicious code.

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

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.

As a temporary measure, you should uninstall the ccxte package from your project to prevent exposure to the malicious code.

Utilizing tools like Vulert can help you monitor your dependencies for vulnerabilities in real-time, ensuring you are alerted to any issues promptly.

How To Fix

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

npm uninstall ccxte

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