Malicious Code Vulnerability in nf-nfa-types Package

nf-nfa-types Updated 02 Oct 2025

Summary

31/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6639: Malicious code in nf-nfa-types (npm). Affects nf-nfa-types versions 3.1.2. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The nf-nfa-types package is an npm library designed for working with non-deterministic finite automata (NFA) and their types. It provides functionalities for creating and manipulating NFAs, making it useful for developers working on automata theory and related applications. However, this package has been identified to contain malicious code that could compromise the integrity of applications utilizing it.

Vulnerability Detail

The vulnerability originates from a malicious code injection in version 3.1.2 of the nf-nfa-types package. This code can potentially lead to unauthorized access, data breaches, or other harmful actions within applications that depend on this library. The malicious nature of the code can execute harmful operations without the user's consent, posing significant risks to application security and user data.

How To Fix

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

npm uninstall nf-nfa-types

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 nf-nfa-types package from your project until a secure version is confirmed. You can do this by executing: npm uninstall nf-nfa-types. This will prevent any potential exploitation of the malicious code while you seek alternatives or wait for a fix.

Conclusion

The nf-nfa-types package has been identified with a serious vulnerability due to malicious code in version 3.1.2. It is crucial for developers using this package to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can help in monitoring and managing such vulnerabilities effectively.

See every vulnerability recorded for nf-nfa-types →

Share this vulnerability

FAQ

The nf-nfa-types package is used for creating and manipulating non-deterministic finite automata (NFA) in JavaScript applications.

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

If you cannot update the package immediately, consider removing it from your project as a temporary measure to mitigate risks.

While specific exploits have not been detailed, the presence of malicious code indicates a risk of unauthorized access and potential data breaches.

You can stay informed by using tools like Vulert, which provides real-time monitoring for vulnerabilities in your open-source dependencies.

How To Fix

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

npm uninstall nf-nfa-types

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