Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.8amended

Malicious Package in whiteproject

GHSA-8j7x-pr59-m5h8

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 whiteproject

    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 whiteproject contain obfuscated malware that uploads Discord user tokens to a remote server. This allows attackers to make purchases on behalf of users if they have credit cards linked to their Discord accounts. Recommendation Remove the package from your environment. Review your Discord account access and rotate tokens if possible. If a credit card was linked to a compromised account contact your credit card company.

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

    Amended from ghsa record GHSA-8j7x-pr59-m5h8

  2. Revision 1 · created ·

    Published from osv record GHSA-8j7x-pr59-m5h8

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-8j7x-pr59-m5h8

Advisory: Malicious Package in whiteproject
IDs: GHSA-8j7x-pr59-m5h8
Record: https://patchnext.com/advisories/ghsa-8j7x-pr59-m5h8 (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 whiteproject: affected every version

## Suggested inspection (read-only)
- `npm ls whiteproject --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 whiteproject.
- 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-8j7x-pr59-m5h8 (OSV record GHSA-8j7x-pr59-m5h8 lists affected ranges: npm whiteproject >=0)
- Verified: https://github.com/advisories/GHSA-8j7x-pr59-m5h8 (GitHub-reviewed advisory GHSA-8j7x-pr59-m5h8 lists affected ranges: npm whiteproject >=0)

Commands are suggestions: review each one before running it.

Loading voting…