# CVE-2017-16207: discordi.js is malware

> A malicious npm package exfiltrates Discord login tokens to an external server, compromising user accounts.

- **Severity:** High 7.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jun 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-fv9m-f7w4-889c

## What is CVE-2017-16207?

CVE-2017-16207 is a high-severity vulnerability in HackerOne discordi.js node module, published on 7 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

discordi.js is a malicious module based on the discord.js library that exfiltrates login tokens to pastebin.

Weakness: CWE-506 (Embedded Malicious Code)

## Which versions are affected by CVE-2017-16207?

2 open source packages ship an affected version, including discordi.js. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `discordi.js` | npm | All versions to 14.0.3 | None |
| `discordi.js` | npm | All versions to 14.0.3 | None |

Products: Discordi.js Project Discordi.js.

## How do I fix CVE-2017-16207?

No fix has been published for CVE-2017-16207 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-16207 being exploited?

There is no known exploitation of CVE-2017-16207 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-16207 and fix it if it is affected.

What it is: CVE-2017-16207 is a high-severity vulnerability in HackerOne discordi.js node module, published on 7 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-16207 in the wild and no public exploit code.

Affected packages and fixed versions:
- discordi.js (npm): affected all versions up to 14.0.3; no fix listed
- discordi.js (npm): affected all versions up to 14.0.3; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-16207/ (Markdown: https://insights.sbomify.com/CVE-2017-16207/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-16207
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-16207
- OSV: https://osv.dev/vulnerability/CVE-2017-16207

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-16207/
Summaries are generated and may contain mistakes; the official description above is the record.