Malicious Code Detected in fnatural Package - Security Alert

fnatural Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20728: Malicious code in fnatural (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 fnatural package is a Node.js library designed for natural language processing tasks. It provides various functionalities to analyze and manipulate text data, making it a valuable tool for developers working on applications that require text analysis. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users who incorporate it into their projects.

Vulnerability Detail

The vulnerability in the fnatural package originates from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious nature of the code means that it can execute harmful operations without the user's consent, making it crucial for developers to address this issue promptly.

How To Fix

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

npm uninstall fnatural

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, consider removing the fnatural package from your project until a secure version is released. You can do this by executing the command: npm uninstall fnatural. This will prevent any potential exploitation of the malicious code while you await a fix.

Conclusion

The discovery of malicious code in the fnatural package underscores the importance of maintaining vigilance when using open-source libraries. Developers are urged to update their dependencies regularly and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can safeguard your applications from potential threats.

See every vulnerability recorded for fnatural →

Share this vulnerability

FAQ

The fnatural package is used for natural language processing tasks, allowing developers to analyze and manipulate text data.

The malicious code can execute harmful operations, potentially leading to unauthorized access and data breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

As a temporary measure, you should uninstall the fnatural package to mitigate any risks associated with the malicious code.

Detailed information about the vulnerability can be found in the GitHub repository of the fnatural package or through security advisories related to npm packages.

How To Fix

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

npm uninstall fnatural

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