Critical Malicious Code Vulnerability in fboffline Package

fboffline Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20278: Malicious code in fboffline (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 fboffline package is an npm library designed to facilitate offline functionality for applications, allowing users to access certain features without an internet connection. It is commonly used in web development projects that require offline capabilities. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the fboffline package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code can lead to unauthorized access, data breaches, or even complete takeover of 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 fboffline

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 using alternative packages that provide similar offline functionality without the associated risks. Always ensure to review the security of any third-party libraries before integrating them into your projects.

Conclusion

The fboffline package has been identified as containing malicious code that poses significant security risks. Users are urged to uninstall the package and seek alternatives until a secure version is released. Utilizing tools like Vulert can help monitor for such vulnerabilities in your projects.

See every vulnerability recorded for fboffline →

Share this vulnerability

FAQ

fboffline is an npm package that enables offline capabilities for web applications, allowing users to access certain features without an internet connection.

The malicious code can lead to unauthorized access and potential data breaches, compromising the security of applications that use the package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By uploading your package-lock.json file, you can check for vulnerabilities without needing to install any software.

Currently, there is no patched version available. It is recommended to uninstall the package until a secure version is released.

Immediately uninstall the fboffline package and consider using alternative solutions for offline functionality.

How To Fix

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

npm uninstall fboffline

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