Malicious Code Detected in fsmfun Package - Security Alert

fsmfun Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21013: Malicious code in fsmfun (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 fsmfun package is an npm library designed for state machine functionality in JavaScript applications. It offers developers a way to manage complex state transitions in a clean and efficient manner. 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 fsmfun package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code may allow unauthorized access, data exfiltration, or other harmful actions within the application environment. The issue was introduced in version 0 and affects all subsequent versions, making it critical for developers to address this vulnerability promptly.

How To Fix

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

npm uninstall fsmfun

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 avoid using the fsmfun package altogether and implement state management using alternative libraries such as xstate or redux. This will help mitigate the risks associated with the malicious code in fsmfun.

Conclusion

The discovery of malicious code in the fsmfun package poses a serious threat to applications relying on it. Developers are urged to remove this package and consider alternatives to safeguard their applications. Regular monitoring of dependencies using tools like Vulert can help maintain security in the long run.

See every vulnerability recorded for fsmfun →

Share this vulnerability

FAQ

fsmfun is an npm package that provides functionality for managing state machines in JavaScript applications.

The malicious code can lead to unauthorized access and potential data breaches within applications that use the fsmfun package.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities. Simply upload your package-lock.json file to check for vulnerabilities in your application.

Currently, there is no patched version available. It is recommended to remove the package and use alternatives until a fix is released.

Utilizing tools like Vulert can help you monitor your dependencies for vulnerabilities in real-time without needing to access the code or install additional software.

How To Fix

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

npm uninstall fsmfun

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