Malicious Code Detected in fpsview Package - Security Alert

fpsview Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20918: Malicious code in fpsview (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The fpsview package is an npm library designed for rendering and managing views in web applications. It is commonly used for its efficient handling of user interface components. However, recent findings have revealed that this package contains malicious code, posing a significant security risk to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the fpsview package. This code can potentially compromise the security of applications that depend on it, leading to unauthorized access, data breaches, or other malicious activities. The issue was first identified in version 0 of the package, and it is crucial for users to be aware of the risks associated with using this compromised library.

How To Fix

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

npm uninstall fpsview

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

Conclusion

The discovery of malicious code in the fpsview package highlights the importance of maintaining secure dependencies in software development. Users are urged to take immediate action by updating or removing the affected package to safeguard their applications from potential threats.

See every vulnerability recorded for fpsview →

Share this vulnerability

FAQ

fpsview is an npm library used for rendering and managing views in web applications, facilitating efficient user interface component handling.

The malicious code found in fpsview can lead to unauthorized access and potential data breaches in applications that use the package.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities. By checking your package-lock.json file, you can identify if your application is affected. Visit the Vulert playground at Vulert Scanner for a quick assessment without signup.

If immediate updates are not possible, consider uninstalling the fpsview package and using alternative libraries until a secure version is available.

Detailed information about the vulnerability can be found in the GitHub repository of the fpsview package, as well as 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 fpsview

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