Security readout for executives and security teams
Plain-English summary
CVE-2017-16127 describes a malicious npm package, pandora-doomsday, that infected other Node.js modules. The package has been unpublished, but any historical installation should be treated as suspect because local dependencies may have been modified.
Executive priority
Prioritize investigation if the organization used Node.js projects around the package’s availability window. The main business risk is contaminated software supply chain artifacts, not a network-exploitable service flaw.
Technical view
The affected product is the pandora-doomsday Node module, all versions. The CVE maps to CWE-509, malicious code. Provided sources state the module infects other modules and was unpublished; they do not provide CVSS, exploit mechanics, indicators, or a vendor patch.
Likely exposure
Exposure is limited to environments that installed pandora-doomsday directly or indirectly before it was unpublished. Check dependency manifests, lockfiles, SBOMs, historical build logs, and package caches.
Exploitation context
The provided sources do not show active exploitation, and CISA KEV status is false. This is still serious for affected systems because installation itself could modify other modules.
Researcher notes
Evidence is sparse. The public bundle identifies malicious infection behavior, all versions affected, unpublished status, and CWE-509. It does not provide payload details, indicators of compromise, CVSS scoring, or confirmed exploitation.
Mitigation direction
- Remove pandora-doomsday from manifests, lockfiles, caches, and internal package mirrors.
- Replace any dependency that pulled pandora-doomsday into the project.
- Rebuild dependencies from trusted sources in a clean environment.
- Review NodeSecurity or registry guidance for any package-specific handling.
- Treat previously installed dependency trees as potentially tampered until validated.
Validation and detection
- Search dependency manifests, lockfiles, SBOMs, and package inventories for pandora-doomsday.
- Review historical CI and build logs for past installation of the package.
- Inspect internal npm mirrors or caches for retained copies.
- Compare affected dependency directories against fresh trusted installs.
- Confirm production artifacts were rebuilt after removing 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-509: 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-16127 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/482CVE 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.
Replicating Malicious Code (Virus or Worm)
Replicating Malicious Code (Virus or Worm) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.