Malicious Code Vulnerability in dpc-sign Package

dpc-sign Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1718: Malicious code in dpc-sign (npm). Affects dpc-sign versions 100.0.0. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The dpc-sign package is a Node.js library used for digital signing of documents and data. It provides functionalities that allow developers to easily implement signing features in their applications. However, this package has been found to contain malicious code that can compromise the security of applications using it.

Vulnerability Detail

The vulnerability in the dpc-sign package arises from the inclusion of malicious code that can execute unauthorized actions within the user's environment. This code can potentially lead to data breaches, unauthorized access to sensitive information, and other security risks. The malicious nature of this vulnerability was identified by ReversingLabs, which reported that the specific version 100.0.0 of the package is affected. Users of this package should be aware of the risks associated with its use and take immediate action to mitigate potential threats.

How To Fix

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

npm uninstall dpc-sign

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 removing the dpc-sign package from your project until a secure version is released. You can do this by running: npm uninstall dpc-sign. Additionally, you may explore alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the dpc-sign package highlights the importance of regularly monitoring and updating open-source dependencies. Users should take immediate action to mitigate risks associated with this vulnerability by uninstalling the affected package and keeping an eye out for updates.

See every vulnerability recorded for dpc-sign →

Share this vulnerability

FAQ

The dpc-sign package is used for digital signing of documents and data in Node.js applications.

You can use Vulert, which monitors open-source vulnerabilities in your software. By using the Vulert playground, you can check if your application is affected without requiring access to the code or installation.

If you are using version 100.0.0 of dpc-sign, it is crucial to uninstall the package and monitor for updates or patches from the maintainers.

Detailed information about this vulnerability can be found in the GitHub repository of the malicious packages or through security advisories from trusted sources.

As of now, there is no patched version available. It is recommended to monitor the package repository for updates.

How To Fix

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

npm uninstall dpc-sign

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