Malicious Code Detected in fssp-request Package - Security Alert

fssp-request Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21015: Malicious code in fssp-request (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The fssp-request package is an npm library designed for making HTTP requests with a focus on simplicity and ease of use. It is utilized in various applications to facilitate communication with APIs and web services. However, recent findings have revealed that this package contains malicious code, posing a significant security risk to users and their applications.

Vulnerability Detail

The vulnerability in the fssp-request package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code may allow unauthorized access to sensitive data, facilitate data exfiltration, or enable other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall fssp-request

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, users can remove the fssp-request package from their project until a secure version is released. This can be done by executing the command: 'npm uninstall fssp-request'. Alternatively, consider using a different package that provides similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the fssp-request package highlights the importance of regularly monitoring and updating open-source dependencies. Users should take immediate action to secure their applications by updating or removing the affected package. Utilizing tools like Vulert can help in monitoring vulnerabilities in real-time.

See every vulnerability recorded for fssp-request →

Share this vulnerability

FAQ

fssp-request is an npm library used for making HTTP requests in a straightforward manner.

The malicious code can potentially compromise application security, allowing unauthorized access to sensitive data.

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

Users are encouraged to check for updates to the fssp-request package and apply them as soon as they are available.

If an immediate update is not possible, consider removing the package or using an alternative library until a secure version is released.

How To Fix

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

npm uninstall fssp-request

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