Malicious Code Detected in dispress Package - Security Alert

dispress Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18501: Malicious code in dispress (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The dispress package is a Node.js library designed for web development, providing various functionalities for managing and deploying web applications. It is widely used in the npm ecosystem due to its ease of integration and robust features. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the dispress package originates from the inclusion of malicious code that can compromise the security of applications using it. This code may lead to unauthorized access, data breaches, or other harmful effects on the system. The malicious nature of this code makes it imperative for developers to act swiftly to mitigate potential risks associated with its use.

How To Fix

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

npm uninstall dispress

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 measure, you can remove the dispress package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall dispress'. This will help mitigate any immediate risks associated with the malicious code.

Conclusion

The discovery of malicious code in the dispress package highlights the importance of regularly monitoring and updating dependencies in software projects. Developers are urged to take immediate action to secure their applications by updating or removing the affected package.

See every vulnerability recorded for dispress →

Share this vulnerability

FAQ

dispress is a Node.js library used for web development, offering various features for managing web applications.

The malicious code can lead to unauthorized access and potential data breaches in applications using the dispress package.

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.

Yes, it is recommended to update to the latest secure version of dispress to mitigate the vulnerability.

As a workaround, you can uninstall the dispress package to prevent any potential security risks until a secure version is available.

How To Fix

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

npm uninstall dispress

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