Critical Malicious Code Vulnerability in fca Package

fca Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20282: Malicious code in fca (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 fca package is a Node.js library commonly used in various applications for its functionality in facilitating certain operations. It is designed to enhance performance and streamline processes within JavaScript environments. However, the package has been identified to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the fca package, which was introduced in version 0 and affects all subsequent versions. This malicious code can lead to unauthorized access, data breaches, and potential exploitation of the affected systems. Users of the fca package are at risk of having their applications compromised, which could result in severe consequences including loss of sensitive data and damage to the application's integrity.

How To Fix

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

npm uninstall fca

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 measure, consider removing the fca package from your project until a secure version is available. You can do this by executing 'npm uninstall fca' in your terminal.

Conclusion

The fca package has been identified to contain malicious code, posing a significant threat to applications that utilize it. It is crucial for developers to update the package to a secure version or remove it from their projects to mitigate risks. Regular monitoring for vulnerabilities using tools like Vulert can help maintain application security.

See every vulnerability recorded for fca →

Share this vulnerability

FAQ

The fca package is a Node.js library used for various operations in JavaScript applications.

The malicious code can lead to unauthorized access and exploitation of systems using the fca package.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Consider removing the fca package from your project as a temporary workaround until a secure version is available.

Detailed information about the vulnerability can be found in the Open Source Vulnerability database at https://github.com/ossf/malicious-packages/blob/main/osv/malicious/npm/fca/MAL-2025-20282.json.

How To Fix

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

npm uninstall fca

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