Malicious Code Detected in drscomm Package - Security Alert

drscomm Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18837: Malicious code in drscomm (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 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 drscomm package is an npm library designed for communication-related functionalities. It is utilized by developers to facilitate various messaging and data transfer tasks within applications. However, this package has been identified to contain malicious code, posing a significant security risk to users and their applications.

Vulnerability Detail

The vulnerability in the drscomm package originates from the inclusion of malicious code that can compromise the integrity and security of applications using this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious nature of the code was confirmed by Amazon Inspector, which flagged the package for its security risks.

How To Fix

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

npm uninstall drscomm

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, you can remove the drscomm package from your project until a secure version is released. Use the following command to uninstall it: 'npm uninstall drscomm'. Consider using alternative packages that provide similar functionality without the security risks.

Conclusion

The discovery of malicious code in the drscomm package poses a serious threat to applications utilizing this library. It is essential to update or remove the package to safeguard your application from potential security breaches. Regular monitoring for vulnerabilities using tools like Vulert can help maintain application security.

See every vulnerability recorded for drscomm →

Share this vulnerability

FAQ

The drscomm package is used for communication functionalities in applications, enabling messaging and data transfer.

The malicious code was detected by Amazon Inspector, which identified security risks within the package.

Using the drscomm package can lead to unauthorized access, data breaches, and other harmful actions within your application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

npm uninstall drscomm

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