Critical Malicious Code Vulnerability in fp_editor_v2 Package

fp_editor_v2 Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20915: 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 an npm library designed for editing and managing various file types. It offers features such as file manipulation, formatting, and user-friendly interfaces for developers. However, it has been identified to contain malicious code that poses significant security risks to applications utilizing this package.

Vulnerability Detail

The vulnerability in the fp_editor_v2 package arises from the inclusion of malicious code that can compromise the integrity and security of applications. This code can lead to unauthorized access, data breaches, or even system control by malicious actors. The issue originates from version 0 of the package and affects all subsequent versions, making it critical for users to take immediate action.

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, users are advised to remove the fp_editor_v2 package from their projects until a secure version is released. This can be done using the command: npm uninstall fp_editor_v2. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The fp_editor_v2 package contains a critical vulnerability due to malicious code, posing significant risks to applications. Immediate action is required to mitigate these risks by updating or removing the package. Users are encouraged to utilize tools like Vulert for ongoing monitoring of vulnerabilities.

See every vulnerability recorded for fp_editor_v2 →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to sensitive data and control over the application.

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.

Currently, there is no patch available. Users should monitor the package repository for updates.

If immediate removal is not possible, ensure to limit the package's permissions and monitor your application closely for any suspicious activity.

Yes, you can report vulnerabilities to the package maintainers or through platforms like GitHub to help improve security.

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