Malicious Code Detected in flow_trigger_connector Package

flow_trigger_connector Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20717: Malicious code in flow_trigger_connector (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The flow_trigger_connector package is an npm library designed to facilitate the integration of various triggers in workflows. It is commonly used in applications that require automated responses to specific events. However, this package has been identified to contain malicious code, posing significant risks to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the flow_trigger_connector package, which was introduced in version 0. This malicious code can potentially compromise the security of applications that depend on this package, leading to unauthorized access, data breaches, or other harmful actions. The origin of this issue is linked to the package's codebase, which has been tampered with to include harmful functionalities.

How To Fix

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

npm uninstall flow_trigger_connector

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 flow_trigger_connector package from your project until a secure version is released. Use the following command to uninstall the package: npm uninstall flow_trigger_connector.

Conclusion

The flow_trigger_connector package has been identified to contain malicious code, posing a significant risk to applications that utilize it. It is essential to take immediate action by updating or removing the package to safeguard your application from potential threats.

See every vulnerability recorded for flow_trigger_connector →

Share this vulnerability

FAQ

The flow_trigger_connector package is an npm library used for integrating triggers in automated workflows within applications.

The malicious code found in the flow_trigger_connector package can lead to unauthorized access and potential data breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

Currently, there is no specific patched version mentioned, but it is crucial to monitor the package repository for updates.

If immediate updates are not possible, consider removing the package as a temporary measure until a secure version is available.

How To Fix

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

npm uninstall flow_trigger_connector

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