Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.8amended

Malicious Package in foever

GHSA-j3qq-qvc8-c6g7

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm foever

    Affected
    every version
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

All versions of foever are considered malicious. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When executed, the package calls home to a Command and Control server to execute arbitrary commands. Recommendation This package was published to the npm Registry for a very short period of time. If you happen to find it in your environment you should revoke and rotate all credentials found on the compromised machine, as well as completely erase the affected machine and reinstall your Operating System.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-j3qq-qvc8-c6g7

  2. Revision 1 · created ·

    Published from osv record GHSA-j3qq-qvc8-c6g7

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-j3qq-qvc8-c6g7

Advisory: Malicious Package in foever
IDs: GHSA-j3qq-qvc8-c6g7
Record: https://patchnext.com/advisories/ghsa-j3qq-qvc8-c6g7 (revision 2, source checked 26 Oct 2026, 12:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm foever: affected every version

## Suggested inspection (read-only)
- `npm ls foever --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on foever.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-j3qq-qvc8-c6g7 (OSV record GHSA-j3qq-qvc8-c6g7 lists affected ranges: npm foever >=0)
- Verified: https://github.com/advisories/GHSA-j3qq-qvc8-c6g7 (GitHub-reviewed advisory GHSA-j3qq-qvc8-c6g7 lists affected ranges: npm foever >=0)

Commands are suggestions: review each one before running it.

Loading voting…