Critical Vulnerability Detected in doctorme: Malicious Code Injection

doctorme Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18574: Malicious code in doctorme (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 'doctorme' package is an npm library designed for document management and processing. It provides functionalities that allow developers to integrate document handling features into their applications. However, recent findings have revealed that this package contains malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability in the 'doctorme' package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code can lead to unauthorized access, data breaches, and potential exploitation of the affected systems. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall doctorme

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 measure, users are advised to remove the 'doctorme' package from their projects until a secure version is released. This can be done using the command: 'npm uninstall doctorme'. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The 'doctorme' package has been identified to contain malicious code, posing a significant threat to users. It is crucial to take immediate action by removing the package and monitoring for updates. Utilizing tools like Vulert can aid in identifying vulnerabilities in your applications effectively.

See every vulnerability recorded for doctorme →

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access and potential exploitation of user data.

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

As of now, there is no patched version available. Users should monitor the package repository for updates.

If immediate removal is not possible, consider isolating the affected components and enhancing security measures until a fix is available.

Vulert uses package-lock.json to monitor and alert in real-time for open-source vulnerabilities, providing a proactive approach to security.

How To Fix

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

npm uninstall doctorme

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