Malicious code in happy-dlscord.js (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-4575
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (2d183bf51c0f2be0102a7a7aeeda661f895e3b075f183d76d5f0f77c09c70860) The package name 'happy-dlscord.js' is a one-character edit of the top-tier npm package 'discord.js' and ships a near-verbatim fork of the upstream library with an injected payload in src/client/Client.js. In Client.prototype.login(), once the client emits 'ready', the package POSTs the caller's Discord bot token to a hardcoded Discord webhook (https://discord.com/api/webhooks/1508514263197552690/...), wrapped in a JSON body containing the bot tag, id, and timestamp, with Arabic-labeled fields including '🔑 التوكن المفرز' formatting the token in spoiler tags. The webhook endpoint is unrelated to the package's stated purpose and is controlled by the attacker. Any developer who installs this package and calls client.login(token) — the standard, mandatory entry point of the library — silently surrenders their bot token to a third party, fully compromising the Discord bot (read all guild messages, send messages as the bot, modify the bot's account, persist beyond simple uninstall). Three independent block signals are present: typosquat of a top-100 package, hardcoded attacker-controlled exfiltration destination, and automatic firing on the library's primary documented API. ## Source: ghsa-malware (370dc741a074186282148bb83e278321f7508c6e5ff3f75d1c098f8252b9fe58) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
- Source published
- 25 May 2026 19:02:13 UTC
- Source modified
- 20 Aug 2026 12:30:11 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.