Malicious Code Detected in ezedit Package - Security Risk Alert

ezedit Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20116: Malicious code in ezedit (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The ezedit package is a JavaScript library available in the npm ecosystem, designed to facilitate editing functionalities in web applications. It is widely used for its ease of integration and user-friendly interface. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the ezedit package, which was introduced in version 0 and affects all subsequent versions. This malicious code can lead to unauthorized access, data breaches, and potential exploitation of the systems that rely on this package. Users of ezedit are at risk of having their applications compromised, which could result in severe consequences, including loss of sensitive data and damage to reputation.

How To Fix

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

npm uninstall ezedit

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 workaround, you can replace the ezedit package with an alternative library that offers similar editing functionalities. Consider using packages like 'quill' or 'tinymce' that are known for their security and reliability.

Conclusion

The discovery of malicious code in the ezedit package highlights the importance of maintaining secure dependencies in software development. Users are advised to take immediate action to mitigate risks by uninstalling the affected package and considering secure alternatives. Regular monitoring for vulnerabilities is essential to safeguard applications.

See every vulnerability recorded for ezedit →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to user data and system resources, making it a significant security threat.

You can use Vulert to monitor and alert in real-time for open-source vulnerabilities. Visit Vulert Scanner to check if your application is affected without needing to sign up.

Immediately uninstall the ezedit package and replace it with a secure alternative. Ensure to review your application for any potential security breaches.

Yes, alternatives like 'quill' and 'tinymce' are recommended for their robust features and security.

Regularly check for vulnerabilities, especially after updates or when adding new packages. Tools like Vulert can help automate this process.

How To Fix

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

npm uninstall ezedit

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