Critical Malicious Code Vulnerability in fxcess Package

fxcess Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21094: Malicious code in fxcess (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 fxcess package is an npm library designed for specific functionalities within JavaScript applications, often utilized for enhancing user experiences or managing data. However, it has been identified to contain malicious code that compromises the security of applications relying on it. This vulnerability poses a significant risk to developers and users alike, as it can lead to unauthorized access or data breaches.

Vulnerability Detail

The vulnerability in the fxcess package originates from the inclusion of malicious code that was intentionally introduced in version 0. This code can execute harmful operations without the user's consent, potentially leading to data theft, unauthorized access, or other malicious activities. The presence of such code raises serious concerns about the integrity and security of applications using this package.

How To Fix

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

npm uninstall fxcess

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 may consider removing the fxcess package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall fxcess'. Additionally, monitor your application for any unusual behavior that may indicate exploitation of this vulnerability.

Conclusion

The fxcess package has been identified to contain malicious code, posing significant security risks to applications that utilize it. It is essential to update to a patched version or remove the package entirely to safeguard your application. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for fxcess →

Share this vulnerability

FAQ

The fxcess package is an npm library used in JavaScript applications for various functionalities, but it has been compromised with malicious code.

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 requiring any signup.

The malicious code can lead to unauthorized access, data breaches, and other harmful operations that compromise the security of your application.

Yes, it is recommended to update the fxcess package to the latest version to mitigate the security risks associated with the malicious code.

If immediate updates are not possible, consider uninstalling the fxcess package and monitoring your application for any suspicious activity.

How To Fix

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

npm uninstall fxcess

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