Critical Malicious Code Vulnerability in fathom-fox (npm)

fathom-fox Updated 02 Oct 2025

Summary

22/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6159: Malicious code in fathom-fox (npm). Affects fathom-fox versions 1.0.0 – 3.7.3. 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 fathom-fox package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers for various tasks, but it has been identified to contain malicious code that compromises the security of any system where it is installed. This vulnerability poses a significant risk to users, as it can lead to unauthorized access and control over affected systems.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the fathom-fox package. This code can compromise any computer that has the package installed, allowing attackers to gain full control over the system. The ramifications include potential data breaches, unauthorized access to sensitive information, and the risk of further malware installation. Users are advised to treat any system with this package as fully compromised.

How To Fix

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

npm uninstall fathom-fox

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

Currently, there are no effective workarounds to mitigate the risks posed by the fathom-fox package. The only recommended action is to uninstall the package and secure the system.

Conclusion

The fathom-fox package has been identified as containing malicious code that poses a serious security risk. Users are strongly advised to uninstall the package and secure their systems to prevent unauthorized access. Regular monitoring for vulnerabilities using tools like Vulert can help maintain application security.

See every vulnerability recorded for fathom-fox →

Share this vulnerability

FAQ

fathom-fox is an npm package used in JavaScript applications, but it has been found to contain malicious code.

You should immediately uninstall the fathom-fox package and rotate any sensitive information stored on your system.

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

Keeping fathom-fox installed can lead to unauthorized access, data breaches, and further malware infections.

As of now, there is no patched version available. The best course of action is to remove the package.

How To Fix

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

npm uninstall fathom-fox

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