Malicious Code Detected in exprses Package - Security Alert

exprses Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20099: Malicious code in exprses (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The exprses package is a Node.js library commonly used for building web applications and APIs. It provides a range of functionalities that simplify the development process. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The exprses package has been identified to contain malicious code, which can compromise the integrity and security of applications using this library. This vulnerability originated from a malicious actor who injected harmful code into the package, potentially leading to unauthorized access, data breaches, or other malicious activities. It is crucial for developers to be aware of this issue to safeguard their applications.

How To Fix

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

npm uninstall exprses

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 exprses package from your project until a secure version is available. You can do this by executing the command: 'npm uninstall exprses'. Alternatively, you can explore other similar packages that do not have known vulnerabilities.

Conclusion

The exprses package has been found to contain malicious code, posing serious security risks to applications. It is imperative for developers to update to a patched version or consider alternative solutions to mitigate these risks. Regular monitoring for vulnerabilities is essential to maintain application security.

See every vulnerability recorded for exprses →

Share this vulnerability

FAQ

The exprses package is used for building web applications and APIs in Node.js, providing various functionalities to streamline development.

The malicious code was discovered by security researchers from Amazon Inspector, who identified the threat during routine checks of open-source packages.

Using the compromised exprses package can lead to unauthorized access to your application, data breaches, and other security vulnerabilities.

Yes, you can use Vulert, which monitors and alerts you in real-time for open-source vulnerabilities in your software. You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner without any signup.

If you cannot update the exprses package immediately, consider removing it from your project or using alternative packages until a secure version is released.

How To Fix

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

npm uninstall exprses

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