Malicious Code Detected in freefroot Package - Security Alert

freefroot Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20947: Malicious code in freefroot (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 freefroot package is an npm library designed for developers to enhance their applications with specific functionalities. However, it has been identified as containing malicious code that poses significant security risks to users and their applications. This vulnerability can lead to unauthorized access, data breaches, and other malicious activities.

Vulnerability Detail

The vulnerability in the freefroot package originates from the inclusion of malicious code that can compromise the integrity of applications using this library. The malicious code can execute harmful operations without the user's consent, potentially leading to data theft, system compromise, or other security incidents. The vulnerability affects all versions of the package starting from version 0.

How To Fix

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

npm uninstall freefroot

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 functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file to detect security issues.

Conclusion

The discovery of malicious code in the freefroot package poses a serious threat to applications using it. It is crucial for developers to take immediate action by uninstalling the package and monitoring their projects for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your software.

See every vulnerability recorded for freefroot →

Share this vulnerability

FAQ

The freefroot package is an npm library used by developers to add specific features to their applications.

The malicious code can execute unauthorized operations, potentially leading to data breaches and system compromises.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

You should uninstall the freefroot package immediately and look for alternative packages or wait for a patched version.

Vulert uses your package-lock.json file to monitor and alert you in real-time about 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 freefroot

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