Critical Malicious Code Vulnerability in @flowfuse/flowfuse Package
Summary
MAL-2025-191453: Malicious code in @flowfuse/flowfuse (npm). Affects @flowfuse/flowfuse versions 2.24.2-375f5e6-202511240929.0. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The @flowfuse/flowfuse package is a JavaScript library available through npm, designed to facilitate various functionalities in web applications. It is widely used for its ease of integration and performance. However, it has recently been identified as containing malicious code that compromises the security of any system where it is installed.
Vulnerability Detail
The vulnerability stems from the presence of embedded malicious code within the @flowfuse/flowfuse package. This code can fully compromise any computer that has the package installed or running, allowing unauthorized access to sensitive information such as secrets and keys. The malicious code was reported by the GHSA (GitHub Security Advisory) and poses a significant risk to users, as it may not be fully eradicated even after the package is removed.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @flowfuse/flowfuseIf 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 risk posed by this vulnerability other than removing the package and securing your system.
Conclusion
The @flowfuse/flowfuse package contains critical malicious code that poses a severe risk to any system where it is installed. Immediate action is required to remove the package and secure sensitive information. Users are encouraged to utilize tools like Vulert for ongoing monitoring of their dependencies.
See every vulnerability recorded for @flowfuse/flowfuse →
FAQ
You should remove the package immediately and rotate any sensitive information that may have been compromised.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
After removing the package, ensure to rotate all secrets and keys stored on the affected computer to prevent unauthorized access.
While removing the package is essential, there is no guarantee that all malicious software installed as a result will be removed.
Regularly monitor your dependencies using tools like Vulert to stay informed about vulnerabilities in your open-source packages.
