Critical Malicious Code Vulnerability in dc-dependencyv Package

dc-dependencyv Updated 02 Oct 2025

Summary

22/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6157: Malicious code in dc-dependencyv (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 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 dc-dependencyv package is an npm library designed to manage dependencies in JavaScript applications. It is commonly used by developers to streamline the process of including and managing external libraries. However, this package has been found to contain embedded malicious code that poses significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the dc-dependencyv package. This code can compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code is classified under CWE-506, indicating that it appears to be intentionally harmful. The ramifications of this vulnerability are severe, as it can lead to full system compromise, making it imperative for users to take immediate action.

How To Fix

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

npm uninstall dc-dependencyv

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 to continue using your application temporarily, consider isolating the environment where the dc-dependencyv package is used. This can be done by using containerization tools like Docker to limit the exposure of your main system. However, this is not a permanent solution and should not replace the removal of the package.

Conclusion

The dc-dependencyv package contains embedded malicious code that poses a significant threat to any system using it. Immediate action is required to remove the package and secure sensitive information. Users are encouraged to utilize tools like Vulert to monitor for vulnerabilities and ensure their applications remain secure.

See every vulnerability recorded for dc-dependencyv →

Share this vulnerability

FAQ

You should immediately remove the dc-dependencyv package and rotate any sensitive information stored on the affected system.

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

Currently, there is no patched version available. The best course of action is to remove the package entirely.

Failing to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

Yes, you can refactor your application to use alternative dependency management solutions that do not pose security risks.

How To Fix

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

npm uninstall dc-dependencyv

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