Critical Malicious Code Vulnerability in flex-plugins Package

flex-plugins Updated 02 Oct 2025

Summary

15/04/2025
CRITICAL
No i
Critical
Not published

MAL-2025-3211: Malicious code in flex-plugins (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 flex-plugins package is a tool used in the npm ecosystem for developing and managing plugins for various applications. It provides developers with a framework to create customizable features and functionalities. However, the package has been identified to contain malicious code that compromises the security of any system it is installed on, making it a significant risk for users.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the flex-plugins package, identified by the ID MAL-2025-3211. This code can fully 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 poses a severe threat, as it may not be fully eradicated even after the package is removed, leaving systems vulnerable to further attacks.

How To Fix

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

npm uninstall flex-plugins

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

There are no effective workarounds for this vulnerability other than removing the package and securing sensitive information. Users should ensure that they do not use the flex-plugins package until a secure version is released.

Conclusion

The flex-plugins package has been identified as containing malicious code that poses a serious security risk. Immediate action is required to remove the package and secure sensitive information. Users are encouraged to utilize tools like Vulert to monitor their applications for vulnerabilities effectively.

See every vulnerability recorded for flex-plugins →

Share this vulnerability

FAQ

You should uninstall the flex-plugins package immediately using 'npm uninstall flex-plugins' and rotate any sensitive information stored on your system.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Failing to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and complete system compromise.

Currently, there is no patched version available for the flex-plugins package. It is recommended to remove the package until a secure version is released.

Vulert monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file, providing real-time insights without requiring code access.

How To Fix

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

npm uninstall flex-plugins

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