Critical Malicious Code Vulnerability in experss Package

experss Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20060: Malicious code in experss (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The experss package is a Node.js framework designed for building web applications and APIs. It is known for its simplicity and flexibility, allowing developers to create robust server-side applications. However, the package has been found to contain malicious code, which poses a significant risk to users and their applications.

Vulnerability Detail

The vulnerability in the experss package arises from the inclusion of malicious code that can compromise the security of applications utilizing this package. This code may lead to unauthorized access, data breaches, or other malicious activities. The vulnerability was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action.

How To Fix

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

npm uninstall experss

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, users can avoid using the experss package and consider utilizing other well-established frameworks such as Express.js, which is a widely used and trusted alternative for building web applications.

Conclusion

The experss package has a critical vulnerability due to the presence of malicious code, which can severely impact applications using it. Users are strongly advised to remove the package and consider alternatives to ensure the security of their applications.

See every vulnerability recorded for experss →

Share this vulnerability

FAQ

The experss package is a Node.js framework used for building web applications and APIs, known for its simplicity and flexibility.

The malicious code in experss can lead to unauthorized access and potential data breaches, posing a significant security risk.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json, it can identify if your application is affected.

The best mitigation strategy is to remove the experss package and replace it with a secure alternative like Express.js.

Utilize tools like Vulert to monitor your dependencies in real-time for any open-source vulnerabilities.

Related vulnerabilities

Recent vulnerabilities recorded for experss.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall experss

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