Critical Malicious Code Vulnerability in node-dpapi1 Package

node-dpapi1 Updated 05 Dec 2025

Summary

05/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192309: Malicious code in node-dpapi1 (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 node-dpapi1 package is an npm library designed to provide access to the Windows Data Protection API (DPAPI) for Node.js applications. It allows developers to securely store and retrieve sensitive data such as passwords and encryption keys. However, this package has been compromised, leading to the introduction of malicious code that can fully compromise any system where it is installed.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the node-dpapi1 package. This code can allow an attacker to gain full control over the affected system, potentially leading to unauthorized access to sensitive information, including secrets and keys stored on the machine. The malicious nature of the code has been confirmed by security researchers, and any system running this package should be considered compromised. Immediate action is required to mitigate risks associated with this vulnerability.

How To Fix

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

npm uninstall node-dpapi1

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 workaround, if you need similar functionality, consider using alternative packages that provide access to the Windows Data Protection API without the associated risks. Always ensure to verify the integrity and security of any package before installation.

Conclusion

The node-dpapi1 package has been identified as containing malicious code that compromises the security of any system where it is installed. Immediate removal of the package and rotation of sensitive information is essential to mitigate potential risks. Always stay vigilant and utilize tools like Vulert to monitor for vulnerabilities in your applications.

See every vulnerability recorded for node-dpapi1 →

Share this vulnerability

FAQ

Immediately uninstall the node-dpapi1 package and rotate any secrets or keys stored on the affected system.

You can use the Vulert playground to check if your application is affected by this vulnerability without any signup required.

Keeping the node-dpapi1 package can lead to unauthorized access to sensitive information and full control of your system by malicious actors.

No, there is currently no patched version available for the node-dpapi1 package. The only solution is to uninstall it.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

How To Fix

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

npm uninstall node-dpapi1

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