Critical Malicious Code Vulnerability in fxa-setting Package

fxa-setting Updated 02 Oct 2025

Summary

22/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6162: Malicious code in fxa-setting (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 fxa-setting package is a component of the npm ecosystem, designed to facilitate user settings management for Firefox Accounts. It is commonly used in web applications that require user authentication and settings storage. However, this package has been identified to contain malicious code, posing significant security risks to any system where it is installed.

Vulnerability Detail

The vulnerability stems from embedded malicious code within the fxa-setting package. This code can compromise the integrity of the host system, allowing unauthorized access to sensitive data such as secrets and keys. The malicious nature of this code means that any system running this package should be considered fully compromised. The origin of this vulnerability is linked to the package's distribution through npm, where it was inadvertently made available to users.

How To Fix

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

npm uninstall fxa-setting

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

There are no effective workarounds for this vulnerability. The only recommended action is to uninstall the fxa-setting package and secure your system.

Conclusion

The fxa-setting package has been identified as containing malicious code that poses a significant risk to any system where it is installed. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to utilize tools like Vulert for ongoing monitoring of their applications.

See every vulnerability recorded for fxa-setting →

Share this vulnerability

FAQ

You should uninstall the fxa-setting package immediately and rotate any secrets or keys stored on your system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

Leaving the fxa-setting package installed can lead to unauthorized access to sensitive data and full compromise of your system.

The best mitigation is to uninstall the package and ensure that your system is secure. There are no effective mitigations while the package remains installed.

You can visit Vulert at https://vulert.com for real-time monitoring and alerts on open-source vulnerabilities in your software.

How To Fix

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

npm uninstall fxa-setting

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