Critical Malicious Code Vulnerability in docbench (npm)

docbench Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18562: Malicious code in docbench (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 docbench package is a tool designed for document benchmarking in Node.js applications. It provides functionalities for measuring and comparing the performance of various document processing tasks. However, it has been identified to contain malicious code that poses significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the docbench package arises from the inclusion of malicious code that can compromise the integrity and security of applications using this package. This code may allow unauthorized access to sensitive data, execute arbitrary commands, or disrupt normal operations. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall docbench

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 remove the docbench package from their project until a secure version is released. This can be done using the following command: npm uninstall docbench. Additionally, consider using alternative benchmarking tools that do not have known vulnerabilities.

Conclusion

The docbench package has been identified as containing malicious code that poses serious security risks. Users are urged to take immediate action by updating or removing the package until a secure version is released. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for docbench →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to sensitive data and execute harmful commands within the user's application.

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

As of now, there is no patched version available. Users should monitor the official repository for updates and apply them as soon as they are released.

If immediate removal is not possible, consider isolating the affected components and implementing strict access controls to mitigate potential risks until a fix is available.

Vulert uses your package-lock.json file to monitor for vulnerabilities in real-time, providing alerts and insights without requiring access to your code or installation.

How To Fix

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

npm uninstall docbench

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