Malicious Package in froever - Critical Vulnerability

froever Updated 02 Oct 2025

Summary

02/09/2020
CRITICAL
No i
Critical
9.8

GHSA-2r8f-2665-3gxq: Malicious Package in froever. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The froever package is an npm package that is used for managing modules in Node.js applications. It provides functionality for installing, updating, and removing modules. The package is widely used in the Node.js ecosystem and is known for its ease of use and convenience. However, all versions of froever have been found to contain malicious code as a preinstall script. This means that when users install the package, the malicious code is executed, leading to potential security breaches and unauthorized access to the user's computer.

Vulnerability Detail

The malicious code in the froever package is designed to take advantage of users making a typo or mistake when typing the name of a module to install. When the package is installed, it downloads a file from a remote server and executes it, opening a backdoor for attackers. This can result in the compromise of the entire computer, with all secrets and keys stored on it being at risk. It is crucial to consider any computer with this package installed as fully compromised, and immediate action should be taken to rotate all affected secrets and keys from a different computer. Removing the package may not guarantee the removal of all malicious software resulting from its installation.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. However, it is crucial to follow the recommended steps mentioned in the 'how_to_fix' section to mitigate the risk and protect the affected systems.

Conclusion

The froever package has been found to contain malicious code as a preinstall script, leading to potential security breaches and unauthorized access to the user's computer. It is crucial to identify and remove this package from all affected computers, rotate all affected secrets and keys, and conduct a thorough security audit to ensure the removal of any potential unauthorized access or compromised systems. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for froever →

Share this vulnerability

FAQ

The impact of this vulnerability is severe. Any computer with the froever package installed should be considered fully compromised, and all secrets and keys stored on it should be rotated immediately.

The malicious code in froever is executed as a preinstall script when the package is installed. It downloads a file from a remote server and executes it, opening a backdoor for attackers.

Removing the froever package may not guarantee the removal of all malicious software resulting from its installation. It is recommended to conduct a thorough security audit to identify any potential unauthorized access or compromised systems.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. It analyzes the package-lock.json file and provides real-time alerts for open-source vulnerabilities.

If your computer is affected by this vulnerability, you should follow the recommended steps mentioned in the 'how_to_fix' section to mitigate the risk and protect your system. Additionally, you can reach out to info@devnack.com for further support on vulnerability remediation.

Related vulnerabilities

Recent vulnerabilities recorded for froever.

How To Fix

No fixed version is published for this vulnerability.

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