Malicious Package in carloprojectlesang

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.

As published by the source; long descriptions are shortened.

All versions of carloprojectlesang 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.

Published by the source

2 Sep 2020, 21:17 UTC

Last modified by the source

9 Jan 2023, 05:03 UTC

Source last checked

26 Oct 2026, 12:08 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-qj2g-642f-4jrv

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-qj2g-642f-4jrv

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

# Patch Next advisory brief: GHSA-qj2g-642f-4jrv

Advisory: Malicious Package in carloprojectlesang
IDs: GHSA-qj2g-642f-4jrv
Record: https://patchnext.com/advisories/ghsa-qj2g-642f-4jrv (revision 2, source checked 26 Oct 2026, 12:08 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 carloprojectlesang: affected every version

## Suggested inspection (read-only)
- `npm ls carloprojectlesang --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 carloprojectlesang.
- 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-qj2g-642f-4jrv (OSV record GHSA-qj2g-642f-4jrv lists affected ranges: npm carloprojectlesang >=0)
- Verified: https://github.com/advisories/GHSA-qj2g-642f-4jrv (GitHub-reviewed advisory GHSA-qj2g-642f-4jrv lists affected ranges: npm carloprojectlesang >=0)

Commands are suggestions: review each one before running it.