Security readout for executives and security teams
Plain-English summary
CVE-2017-16128 concerns the npm package npm-script-demo. Public sources state the module opened a connection to a command-and-control server and was removed from the npm registry.
Executive priority
Treat confirmed presence as urgent supply-chain cleanup. The package was reportedly malicious and removed, but public evidence does not quantify exploitation or business impact.
Technical view
The issue is categorized as CWE-506, embedded malicious code. Affected scope is listed as all versions of the npm-script-demo Node module. No CVSS score, patch version, or detailed technical behavior is provided in the source bundle.
Likely exposure
Exposure is likely limited to projects that installed npm-script-demo before removal, including old lockfiles, private npm mirrors, build caches, or transitive dependency records.
Exploitation context
The source bundle does not show CISA KEV listing or other evidence of active exploitation. The risk comes from the package’s reported command-and-control behavior, not from a published exploit chain.
Researcher notes
Sources provide minimal detail beyond command-and-control behavior, removal from npm, CWE-506, and all-version impact. Avoid assuming payload capabilities, persistence, data theft, or specific indicators without additional vendor evidence.
Mitigation direction
- Remove npm-script-demo from direct and transitive dependencies.
- Regenerate lockfiles after removal and rebuild from trusted sources.
- Block the package in private registries and dependency allowlists.
- Check vendor and npm security guidance for any updated instructions.
- Review affected build and developer systems for possible credential exposure.
Validation and detection
- Search package manifests and lockfiles for npm-script-demo.
- Check private registry mirrors and caches for retained copies.
- Review historical dependency installation logs where available.
- Inspect proxy or egress logs around affected install windows.
- Confirm CI and production builds no longer resolve the package.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-506: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2017-16128 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://nodesecurity.io/advisories/481CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Embedded Malicious Code
Embedded Malicious Code represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.