How severe is GHSA-5x8q-gj67-rhf2?

GHSA-5x8q-gj67-rhf2 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-5x8q-gj67-rhf2?

GHSA-5x8q-gj67-rhf2 affects the following packages: discord_debug_log (npm). Ecosystems affected: npm.

How do I fix GHSA-5x8q-gj67-rhf2?

No patched version of discord_debug_log has shipped for GHSA-5x8q-gj67-rhf2 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-5x8q-gj67-rhf2 in my npm dependencies?

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

How do I mitigate GHSA-5x8q-gj67-rhf2 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-5x8q-gj67-rhf2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-5x8q-gj67-rhf2 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-5x8q-gj67-rhf2 published, and has it been updated?

GHSA-5x8q-gj67-rhf2 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 discord_debug_logGHSA-5x8q-gj67-rhf2

CRITICAL

GHSA-5x8q-gj67-rhf2 is a critical-severity (CVSS 9.8) vulnerability in discord_debug_log. 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.

discord_debug_lognpm

4downloads / week

Description

All versions of discord_debug_log 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	`discord_debug_log`	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 discord_debug_log, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of discord_debug_log has shipped for GHSA-5x8q-gj67-rhf2 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 `discord_debug_log` 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-5x8q-gj67-rhf2 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works