CVE-2017-16128
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe module npm-script-demo opened a connection to a command and control server. It has been removed from the npm registry.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe npm-script-demo package was a malicious module that established outbound connections to a threat actor's command and control server, effectively functioning as a backdoor or remote access mechanism. This represents a supply chain compromise where a malicious package was published to the public npm registry.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 0.0.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check package.json for the malicious packageSearch for 'npm-script-demo' in your project's package.json file, specifically in the dependencies or devDependencies sectionsAffected if The package name npm-script-demo appears in dependencies with version 0.0.1
-
Verify package installation in node_modulesRun 'ls node_modules | grep npm-script-demo' or check if the directory node_modules/npm-script-demo existsAffected if The npm-script-demo directory exists in node_modules
-
Query npm for installed packageRun 'npm list npm-script-demo' or 'npm list --depth=0' to see installed packagesAffected if npm-script-demo appears in the npm list output
-
Check for the specific malicious versionRun 'npm list npm-script-demo --depth=0' and verify if version 0.0.1 is installedAffected if Version 0.0.1 of npm-script-demo is shown as installed
-
Review npm installation logsCheck your npm install logs, build logs, or CI/CD logs for any past installations of npm-script-demoAffected if The package was ever installed in the project history
If npm-script-demo version 0.0.1 is found in package.json, node_modules, or installation history, the environment is affected by this supply chain compromise.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedAudit all project dependencies and npm install logs to identify if npm-script-demo was ever installed, remove the package from any systems where found, and conduct forensic review of affected systems for indicators of compromise or unauthorized access.
- Remove the npm-script-demo package from your project dependencies immediately
- Run 'npm uninstall npm-script-demo' to remove the package
- Check your package-lock.json and yarn.lock to ensure the malicious package is not present
- Search your codebase for any references to this package and remove them
- Audit your project for any other unknown or suspicious dependencies
- Consider rotating any credentials or secrets that may have been exposed if the package was installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-16128 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-16128 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data