How severe is GHSA-qj2g-642f-4jrv?

GHSA-qj2g-642f-4jrv has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-qj2g-642f-4jrv?

GHSA-qj2g-642f-4jrv affects the following packages: carloprojectlesang (npm). Ecosystems affected: npm.

How do I fix GHSA-qj2g-642f-4jrv?

No patched version of carloprojectlesang has shipped for GHSA-qj2g-642f-4jrv yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-qj2g-642f-4jrv in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for carloprojectlesang, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-qj2g-642f-4jrv if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-qj2g-642f-4jrv actively exploited in the wild?

No public exploit code has been indexed for GHSA-qj2g-642f-4jrv yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-qj2g-642f-4jrv published, and has it been updated?

GHSA-qj2g-642f-4jrv was published on September 2, 2020 and was last updated on September 30, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

CRITICAL severity

Malicious Package in carloprojectlesangGHSA-qj2g-642f-4jrv

CRITICAL

GHSA-qj2g-642f-4jrv is a critical-severity (CVSS 9.8) vulnerability in carloprojectlesang. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 2, 2020

Updated

Sep 30, 2021

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Sep 30, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

carloprojectlesangnpm

5downloads / week

Description

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.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`carloprojectlesang`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for carloprojectlesang, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of carloprojectlesang has shipped for GHSA-qj2g-642f-4jrv yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-qj2g-642f-4jrv in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works