Critical Malicious Code Vulnerability in doxmaster Package

doxmaster Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18720: Malicious code in doxmaster (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 doxmaster package is an npm library designed for document management and manipulation. It provides various functionalities for handling document formats and streamlining workflows. However, the package has been identified to contain malicious code that poses significant security risks to applications utilizing it.

Vulnerability Detail

The vulnerability in the doxmaster package originates from the inclusion of malicious code that can compromise the integrity and security of applications. This code can lead to unauthorized access, data breaches, and potential exploitation of user data. The malicious nature of the code was confirmed by security researchers, and it affects all versions starting from 0.

How To Fix

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

npm uninstall doxmaster

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, consider using alternative packages that provide similar functionalities without the associated risks. Always review the security status of any package before integrating it into your project.

Conclusion

The doxmaster package has been identified to contain malicious code, posing serious security risks to applications. It is crucial for developers to remove the package and consider alternatives while keeping an eye on updates from the package maintainers. Tools like Vulert can assist in monitoring vulnerabilities effectively.

See every vulnerability recorded for doxmaster →

Share this vulnerability

FAQ

Doxmaster is an npm package used for document management and manipulation, offering various features for handling document formats.

The vulnerability is classified as malicious code, which can lead to unauthorized access and data breaches.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

It is recommended to remove the doxmaster package from your project and look for alternative solutions until a secure version is available.

Utilize tools like Vulert, which can monitor your package-lock.json file for vulnerabilities and provide real-time alerts.

How To Fix

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

npm uninstall doxmaster

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