Malicious Code Vulnerability in fca-raihan Package

fca-raihan Updated 30 Sep 2026

Summary

30/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17328: Malicious code in fca-raihan (npm). Affects fca-raihan versions 37.2.5 – 37.2.6. 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 fca-raihan package is an npm library designed for messaging and end-to-end encryption (E2EE) functionalities. It allows developers to integrate secure messaging features into their applications. However, the package has a significant vulnerability due to its dependency management, which can lead to the installation of malicious code from an unverified source.

Vulnerability Detail

The vulnerability arises from the fca-raihan package declaring a dependency on itself with a source from GitHub. This off-registry dependency lacks a reference pin and integrity check, meaning that during installation, npm fetches the latest code from the GitHub repository. This allows the repository owner to modify the code at any time, potentially introducing malicious scripts. The self-referential nature of the dependency can lead to unintended code execution during normal installs, posing a risk to users who rely on this package for secure messaging.

How To Fix

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

npm uninstall fca-raihan

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, avoid using the fca-raihan package until the dependency issue is resolved. Consider using alternative packages that provide similar messaging and E2EE functionalities without the dependency risks.

Conclusion

The fca-raihan package has a critical vulnerability due to its self-referential dependency, which can lead to the installation of malicious code. Users are advised to update to the latest version or consider alternative packages to ensure the security of their applications. Regular monitoring and updates are essential for maintaining a secure environment.

See every vulnerability recorded for fca-raihan →

Share this vulnerability

FAQ

The main issue is that it declares a self-referential dependency that can fetch unverified code from GitHub, potentially leading to the installation of malicious scripts.

You can use Vulert, which monitors open-source vulnerabilities in your software. By using the Vulert playground, you can check if your application is affected without needing to sign up.

Using the fca-raihan package poses risks of executing malicious code, which can compromise the security of your application and its users.

Yes, updating to the latest version of the fca-raihan package will help mitigate the vulnerability.

If you cannot update the package right away, consider using alternative packages or implementing a temporary workaround by avoiding the use of fca-raihan.

How To Fix

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

npm uninstall fca-raihan

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