# CVE-2017-16127: pandora-doomsday is malware

> The pandora-doomsday npm module maliciously infects other modules, requiring developers to remove it to prevent compromise.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 16 Sep 2024
- **Also known as:** GHSA-428f-mh7w-6w2x

## What is CVE-2017-16127?

CVE-2017-16127 is a critical vulnerability in HackerOne pandora-doomsday 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

The module pandora-doomsday infects other modules. It's since been unpublished from the registry.

Weakness: CWE-276 (Incorrect Default Permissions), CWE-509 (Replicating Malicious Code (Virus or Worm))

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

2 open source packages ship an affected version, including pandora-doomsday. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pandora-doomsday` | npm | From 0.0.0 | None |
| `pandora-doomsday` | npm | From 0.0.0 | None |

Products: Pandora-Doomsday Project Pandora-Doomsday.

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

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

## Is CVE-2017-16127 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-16127 is a critical vulnerability in HackerOne pandora-doomsday 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-16127 in the wild and no public exploit code.

Affected packages and fixed versions:
- pandora-doomsday (npm): affected from 0.0.0; no fix listed
- pandora-doomsday (npm): affected from 0.0.0; 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-16127/ (Markdown: https://insights.sbomify.com/CVE-2017-16127/index.md)
```

## Sources

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

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