Malicious Code Detected in emr-ccd Package - Security Alert

emr-ccd Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19631: Malicious code in emr-ccd (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 emr-ccd package is an npm library designed for managing and processing data related to electronic medical records. It offers functionalities such as data transformation, integration with various health data systems, and compliance with healthcare regulations. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the emr-ccd package stems from the presence of malicious code that can compromise the integrity and security of applications using this package. This code may allow unauthorized access to sensitive data, lead to data breaches, or facilitate other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall emr-ccd

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, consider removing the emr-ccd package from your project until a secure version is released. You can uninstall it using the command: 'npm uninstall emr-ccd'. Additionally, explore alternative packages that provide similar functionality without the associated risks.

Conclusion

The emr-ccd package has been identified as containing malicious code, posing serious security risks to applications. It is crucial for developers to take immediate action by updating or removing the package to protect sensitive data and maintain application integrity.

See every vulnerability recorded for emr-ccd →

Share this vulnerability

FAQ

The emr-ccd package is used for managing and processing electronic medical records data, facilitating integration with health data systems.

You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

If immediate updates are not feasible, consider removing the package and using alternative solutions until a secure version is available.

Using the compromised package may lead to unauthorized access to sensitive data, data breaches, and other malicious activities.

How To Fix

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

npm uninstall emr-ccd

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