Malicious Code Detected in fispatch Package - Security Risk Alert

fispatch Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20617: Malicious code in fispatch (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 fispatch package is an npm library designed for handling specific functionalities within JavaScript applications. It is commonly used for its ease of integration and efficiency in managing data flows. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the fispatch package stems from the inclusion of malicious code that can compromise the integrity and security of applications using this library. This code can lead to unauthorized access, data breaches, or other malicious activities that could severely impact users and organizations. The issue was introduced in version 0 and affects all subsequent versions.

How To Fix

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

npm uninstall fispatch

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 fispatch package from your project by running the following command in your terminal: npm uninstall fispatch. This will prevent any malicious code from executing in your application until a secure alternative is implemented.

Conclusion

The discovery of malicious code in the fispatch package highlights the importance of regularly auditing dependencies in software projects. It is essential to remove the affected package and monitor for updates or alternatives to ensure the security of your applications.

See every vulnerability recorded for fispatch →

Share this vulnerability

FAQ

fispatch is an npm package used for specific functionalities in JavaScript applications, but it has been found to contain malicious code.

The malicious code was identified through security audits and reports from security tools like Amazon Inspector.

Using fispatch can lead to unauthorized access, data breaches, and other security vulnerabilities in your application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall fispatch

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