# CVE-2017-16128: npm-script-demo is malware

> A malicious npm package communicated with a command and control server, allowing attackers to execute code or steal data from users who installed it.

- **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-322m-p39j-r5m2

## What is CVE-2017-16128?

CVE-2017-16128 is a critical vulnerability in HackerOne npm-script-demo 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 npm-script-demo opened a connection to a command and control server. It has been removed from the npm registry.

Weakness: CWE-276 (Incorrect Default Permissions), CWE-506 (Embedded Malicious Code)

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

2 open source packages ship an affected version, including npm-script-demo. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `npm-script-demo` | npm | All versions | None |
| `npm-script-demo` | npm | All versions | None |

Products: Npm-Script-Demo Project Npm-Script-Demo.

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

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

## Is CVE-2017-16128 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-16128 is a critical vulnerability in HackerOne npm-script-demo 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-16128 in the wild and no public exploit code.

Affected packages and fixed versions:
- npm-script-demo (npm): affected all versions; no fix listed
- npm-script-demo (npm): affected all versions; 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-16128/ (Markdown: https://insights.sbomify.com/CVE-2017-16128/index.md)
```

## Sources

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

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