Malicious Package in foever - Critical Vulnerability

foever Updated 02 Oct 2025

Summary

01/09/2020
CRITICAL
No i
Critical
9.8

GHSA-j3qq-qvc8-c6g7: Malicious Package in foever. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The foever package is an npm package that is used for managing modules in Node.js applications. It provides functionality for installing and managing dependencies. However, all versions of foever have been identified as malicious. This package is designed to exploit users who make typographical errors when typing the name of a module to install. When executed, the package connects to a Command and Control server to execute arbitrary commands on the compromised machine. This poses a significant security risk to affected systems.

Vulnerability Detail

The vulnerability in the foever package allows an attacker to gain control over the compromised machine by executing arbitrary commands. This can lead to unauthorized access, data theft, and potential damage to the system. The package disguises itself as a legitimate module, tricking users into installing it. Once installed, it establishes a connection to a remote server, enabling the attacker to remotely execute commands on the compromised machine. The package was published to the npm Registry for a short period of time, but it is crucial to take immediate action if it is found in your environment.

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 for this vulnerability. It is essential to follow the recommended steps to fix the issue and ensure the security of your system.

Conclusion

The foever package has been identified as a malicious package that can compromise the security of your system. If you find this package in your environment, it is crucial to take immediate action to revoke and rotate credentials, erase the affected machine, and reinstall the Operating System. Regularly updating and patching your software and dependencies is essential to prevent similar vulnerabilities in the future. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for foever →

Share this vulnerability

FAQ

The foever package is an npm package used for managing modules in Node.js applications. However, all versions of foever have been identified as malicious.

The vulnerability allows an attacker to execute arbitrary commands on the compromised machine, potentially leading to unauthorized access, data theft, and system damage.

To fix the vulnerability, you should revoke and rotate all credentials found on the compromised machine, completely erase the affected machine and reinstall the Operating System, and remove the foever package from your project's dependencies.

There is no specific workaround for this vulnerability. It is crucial to follow the recommended steps to fix the issue and ensure the security of your system.

To prevent similar vulnerabilities, it is important to regularly update and patch your software and dependencies. Stay vigilant and verify the authenticity of packages before installing them.

Related vulnerabilities

Recent vulnerabilities recorded for foever.

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