Malicious Code Detected in docxead Package - Security Alert

docxead Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18586: Malicious code in docxead (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The docxead package is an npm library designed for manipulating and generating DOCX files. It provides various functionalities that allow developers to create and modify Word documents programmatically. 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 docxead package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. 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 docxead

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 an immediate workaround, consider removing the docxead package from your project until a secure version is released. You can do this by running the command: 'npm uninstall docxead'. Additionally, explore alternative libraries that provide similar functionalities without the associated risks.

Conclusion

The discovery of malicious code in the docxead package highlights the importance of vigilance when using open-source libraries. Users are encouraged to update or remove the package to mitigate potential risks and to utilize monitoring tools like Vulert to stay informed about vulnerabilities.

See every vulnerability recorded for docxead →

Share this vulnerability

FAQ

docxead is an npm package used for creating and manipulating DOCX files in Node.js applications.

The malicious code was identified by security researchers from Amazon Inspector, who reported it as part of their ongoing monitoring of open-source packages.

Using the compromised package can lead to security vulnerabilities, including unauthorized access to sensitive data and potential exploitation of the application.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can check your application for vulnerabilities without any signup at the Vulert playground.

Regularly updating your dependencies, using tools like Vulert for monitoring, and conducting security audits can help prevent vulnerabilities in your applications.

How To Fix

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

npm uninstall docxead

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