Critical Malicious Code Vulnerability in flowframe (npm)

flowframe Updated 02 Oct 2025

Summary

15/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5914: Malicious code in flowframe (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 flowframe package is a JavaScript library available through npm, designed for creating and managing flow-based applications. It offers various functionalities that facilitate the development of interactive and dynamic user interfaces. However, this package has been identified to contain malicious code that poses significant security risks to systems where it is installed.

Vulnerability Detail

The vulnerability originates from the inclusion of embedded malicious code within the flowframe package. This code can compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information, including secrets and keys. The ramifications of this vulnerability are severe, as it may lead to complete control of the affected system by an external entity, making it imperative 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 flowframe

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 recommended to rotate all secrets and keys stored on the compromised system from a different, secure computer.

Conclusion

The flowframe package has been identified as containing malicious code that poses a significant security threat. Users must act swiftly to remove the package and secure their systems to prevent unauthorized access. Regular monitoring for updates and vulnerabilities is essential to maintain system integrity.

See every vulnerability recorded for flowframe →

Share this vulnerability

FAQ

Flowframe is a JavaScript library used for developing flow-based applications, enabling the creation of interactive user interfaces.

The malicious code can compromise the security of the system, allowing unauthorized access to sensitive information and potentially granting full control to an external entity.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

You should remove the flowframe package from your system immediately and rotate any sensitive information stored on the affected machine.

As of now, there is no patch available. Users are advised to remove the package until a secure version is released.

How To Fix

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

npm uninstall flowframe

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