Critical Malicious Code Vulnerability in vdous Package

vdous Updated 19 Dec 2025

Summary

19/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192645: Malicious code in vdous (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The vdous package is a Node.js library available through npm, designed to facilitate 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 to developers and organizations relying on this package for their projects.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the vdous package, which has been flagged as a serious security threat. Any system running this package is considered fully compromised, with potential unauthorized access to sensitive information such as secrets and keys. The malicious code may allow external entities to gain control over the affected systems, leading to severe data breaches and loss of integrity.

How To Fix

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

npm uninstall vdous

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 posed by the vdous package. The only recommended action is to uninstall the package and secure your system.

Conclusion

The vdous package has been identified as containing malicious code that poses a significant security risk. Immediate action is required to uninstall the package and secure any compromised systems. Utilizing tools like Vulert can help monitor for vulnerabilities in the future.

See every vulnerability recorded for vdous →

Share this vulnerability

FAQ

Immediately uninstall the vdous package using the command npm uninstall vdous and rotate any sensitive information stored on the affected system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

Leaving the vdous package installed can lead to unauthorized access to your system, potential data breaches, and loss of sensitive information.

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

After removing the package, rotate all secrets and keys stored on the affected system and monitor for any unusual activity.

How To Fix

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

npm uninstall vdous

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