Critical Malicious Code Vulnerability in codemirror-5 Package

codemirror-5 Updated 02 Dec 2025

Summary

02/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191557: Malicious code in codemirror-5 (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

codemirror-5 is a popular library used for code editing in web applications. It provides a versatile and customizable code editor that supports various programming languages and features syntax highlighting, autocompletion, and more. However, recent findings have revealed that this package contains malicious code, posing significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the codemirror-5 package. This code can compromise any computer that has the package installed, 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. Users are advised to treat any system running this package as fully compromised, as the removal of the package may not eliminate all traces of the malicious software.

How To Fix

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

npm uninstall codemirror-5

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 this vulnerability other than removing the package entirely. It is crucial to monitor your systems for any signs of compromise after the removal.

Conclusion

The discovery of malicious code within the codemirror-5 package poses a severe threat to users and systems that utilize it. Immediate action is required to uninstall the package and secure any sensitive information. Users should remain vigilant and consider alternative solutions for code editing functionalities.

See every vulnerability recorded for codemirror-5 →

Share this vulnerability

FAQ

You should immediately uninstall the codemirror-5 package and rotate any sensitive information stored on the affected system.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

Failing to remove the package can lead to unauthorized access to your system, potentially compromising sensitive data and exposing your application to further attacks.

The best course of action is to uninstall the package and rotate all secrets and keys. There is no recovery method available as the package is inherently malicious.

Yes, consider looking for alternative code editing libraries that do not have known vulnerabilities and are actively maintained.

How To Fix

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

npm uninstall codemirror-5

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