Critical Malicious Code Vulnerability in dtcp-module (npm)

dtcp-module Updated 02 Oct 2025

Summary

10/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5774: Malicious code in dtcp-module (npm). Affects dtcp-module versions 5.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 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 dtcp-module is a package available in the npm ecosystem, primarily used for various functionalities in JavaScript applications. However, it has been identified as containing malicious code that compromises the security of any system where it is installed. This vulnerability poses a significant risk as it can lead to unauthorized access and control over the affected systems.

Vulnerability Detail

The vulnerability in the dtcp-module originates from the presence of embedded malicious code. This code can fully compromise any computer that has the package installed, allowing attackers to gain control and access sensitive information. The ramifications include potential data breaches, unauthorized access to secrets and keys, and the possibility of further malware installation. The vulnerability is classified under CWE-506, indicating that the product contains code that appears to be malicious in nature.

How To Fix

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

npm uninstall dtcp-module

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

Currently, there are no effective workarounds to mitigate the risks associated with the dtcp-module. The best course of action is to remove the package entirely and ensure that your system is secure.

Conclusion

The dtcp-module package has been identified as containing malicious code that poses a serious security risk. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to monitor their systems and utilize tools like Vulert for ongoing vulnerability management.

See every vulnerability recorded for dtcp-module →

Share this vulnerability

FAQ

You should remove the dtcp-module package immediately and rotate any secrets or keys stored on the affected machine.

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.

As of now, there is no patch available. The recommended action is to remove the package.

Failure to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential further malware infections.

It is not recommended to reinstall dtcp-module until a secure, patched version is released.

How To Fix

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

npm uninstall dtcp-module

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