Critical Malicious Code Vulnerability in dxpress Package

dxpress Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19025: Malicious code in dxpress (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 dxpress package is an npm library designed for building web applications with a focus on performance and ease of use. It provides various utilities and features that streamline the development process. However, it has been identified to contain malicious code, posing a significant security risk to applications that utilize it.

Vulnerability Detail

The dxpress package has been found to include malicious code that can compromise the security of applications using it. This vulnerability originates from the package itself, which was intentionally designed to execute harmful actions. The ramifications of this vulnerability can include unauthorized access to sensitive data, data corruption, and potential system compromise. It is crucial for developers to be aware of this issue to protect their applications from exploitation.

How To Fix

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

npm uninstall dxpress

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 can replace the dxpress package with an alternative library that provides similar functionality without the associated risks. Review your project's dependencies and consider using well-established packages that have a good security track record.

Conclusion

The dxpress package has been identified as containing malicious code, posing a serious threat to applications that utilize it. Developers are urged to remove the package and seek alternatives to safeguard their projects. Continuous monitoring for vulnerabilities is essential to maintain application security.

See every vulnerability recorded for dxpress →

Share this vulnerability

FAQ

dxpress is an npm library used for building web applications, offering various utilities to enhance development efficiency.

The malicious code in dxpress can execute harmful actions, potentially leading to unauthorized access and data compromise.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

Immediately remove the dxpress package from your project and look for alternative libraries to replace its functionality.

Currently, there is no patched version available. It is best to remove the package until a secure alternative is found.

How To Fix

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

npm uninstall dxpress

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