Malicious Code Detected in docuwrite Package - Security Alert

docuwrite Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18585: Malicious code in docuwrite (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 docuwrite package is an npm library designed for document creation and manipulation. It offers various features that allow developers to generate documents programmatically. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the docuwrite package originates from the inclusion of malicious code that can compromise the integrity of applications using this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious nature of this vulnerability makes it critical for users to address it promptly to avoid potential exploitation.

How To Fix

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

npm uninstall docuwrite

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, users can remove the docuwrite package from their project until a secure version is released. This can be done by executing the command: 'npm uninstall docuwrite'. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the docuwrite package highlights the importance of maintaining vigilance when using open-source libraries. Users are urged to take immediate action by updating or removing the package to safeguard their applications from potential threats.

See every vulnerability recorded for docuwrite →

Share this vulnerability

FAQ

docuwrite is an npm package used for creating and manipulating documents programmatically.

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

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

Currently, a patched version is not specified, but users should monitor the package repository for updates.

As a workaround, consider uninstalling the docuwrite package and using alternative libraries 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 docuwrite

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