Malicious Code Detected in fpa-base Package - Security Alert

fpa-base Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20916: Malicious code in fpa-base (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 fpa-base package is an npm library designed for various functionalities within JavaScript applications. It is commonly used for its utility features that enhance application performance. However, recent investigations have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the fpa-base package stems from the inclusion of malicious code that can compromise the security of applications relying on it. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. 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 fpa-base

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 fpa-base package from your project until a secure version is released. You can do this by executing: 'npm uninstall fpa-base'. This will prevent any potential exploitation of the malicious code present in the package.

Conclusion

The discovery of malicious code in the fpa-base package highlights the importance of maintaining secure dependencies in software development. Users are advised to update or remove the package to safeguard their applications from potential threats.

See every vulnerability recorded for fpa-base →

Share this vulnerability

FAQ

fpa-base is an npm package used for various utility functions in JavaScript applications.

The malicious code can lead to unauthorized access and data breaches within applications using the package.

You can use Vulert to monitor and alert for vulnerabilities in your application. Visit Vulert Scanner to check if your application is affected without any signup.

As a temporary measure, you can uninstall the fpa-base package to mitigate risks until a secure version is available.

Utilize tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time, ensuring you are alerted to any issues as they arise.

How To Fix

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

npm uninstall fpa-base

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