Malicious Code Detected in fp.editor.v2 Package - Security Alert

fp.editor.v2 Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20914: Malicious code in fp.editor.v2 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The fp.editor.v2 package is a JavaScript library used in Node.js applications, primarily for editing functionalities. It is designed to enhance user experience by providing rich text editing capabilities. However, this package has been identified to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the fp.editor.v2 package arises from the inclusion of malicious code that can compromise the security of applications using this library. This code can lead to unauthorized access, data breaches, or other malicious activities. The issue originates from the package itself, which has been flagged for containing harmful scripts that execute without user consent.

How To Fix

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

npm uninstall fp.editor.v2

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 remove the fp.editor.v2 package from your project until a secure version is released. You can do this by running the command: 'npm uninstall fp.editor.v2'. Additionally, consider using alternative packages that provide similar functionalities without security risks.

Conclusion

The fp.editor.v2 package has been identified as containing malicious code, which poses a serious threat to applications utilizing it. It is crucial to take immediate action by removing the package and monitoring for updates. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for fp.editor.v2 →

Share this vulnerability

FAQ

The malicious code can execute harmful actions without user consent, potentially leading to data breaches or unauthorized access.

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

As of now, it is recommended to uninstall the affected package until a secure version is released.

Consider removing the package temporarily and using alternative libraries that provide similar functionalities without the associated risks.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, and keep your packages updated to the latest secure versions.

How To Fix

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

npm uninstall fp.editor.v2

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