LiveActive security incident?Get immediate response
CVE Record

CVE-2025-54313: eslint-config-prettier 8.10.1, 9.1.1, 10.1.6, and 10.1.7 has embedded malicious code for a supply chain com...

eslint-config-prettier 8.10.1, 9.1.1, 10.1.6, and 10.1.7 has embedded malicious code for a supply chain compromise. Installing an affected package executes an install.js file that launches the node-gyp.dll malware on Windows.

HighCVSS 7.5Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is a compromised npm package used in JavaScript tooling. Specific eslint-config-prettier versions contained malicious code that ran during installation and launched Windows malware. Risk is highest for developer workstations, CI runners, and build systems that installed the affected versions.

Executive priority

Treat as high priority for engineering and build-security teams. The main business risk is compromise of trusted development or CI systems, which can expose credentials and downstream software integrity.

Technical view

CVE-2025-54313 affects eslint-config-prettier versions 8.10.1, 9.1.1, 10.1.6, and 10.1.7. The package included embedded malicious code: an install.js script that launches node-gyp.dll malware on Windows. It is classified as CWE-506 and scored CVSS 7.5 high.

Likely exposure

Organizations using npm with eslint-config-prettier are exposed if dependency locks, caches, developer machines, or CI environments installed versions 8.10.1, 9.1.1, 10.1.6, or 10.1.7. Evidence in the bundle indicates the malware path is Windows-focused.

Exploitation context

CISA KEV marks CVE-2025-54313 as known exploited. Public reporting in the bundle describes a phishing-led npm maintainer compromise that published malicious package versions. The bundle does not provide evidence of specific victim counts or post-infection attacker objectives.

Researcher notes

The evidence supports a malicious package compromise, not a typical code bug. Focus validation on dependency provenance, install-time execution, Windows endpoints, CI runners, caches, and credential exposure. Do not assume non-Windows impact beyond what sources document.

Mitigation direction

  • Remove affected eslint-config-prettier versions from dependency locks and build images.
  • Follow npm and project maintainer guidance for clean replacement versions.
  • Rebuild Windows developer and CI environments that installed affected versions.
  • Rotate credentials exposed to affected Windows build or developer systems.
  • Purge npm caches and artifact mirrors containing affected packages.

Validation and detection

  • Search package locks for eslint-config-prettier 8.10.1, 9.1.1, 10.1.6, or 10.1.7.
  • Review CI logs for installs of affected versions during the exposure window.
  • Check Windows systems for evidence of node-gyp.dll execution from package install paths.
  • Confirm dependency mirrors no longer serve the affected package versions.
  • Verify remediated builds install only unaffected eslint-config-prettier versions.
Prepared
Confidence
high
Sources
9

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

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 lookup
cve · low confidence lookup

CVE-2025-54313 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
11Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:N2.24.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2025-54313Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
prettiereslint-config-prettier8.10.1, 9.1.1, 10.1.6, 10.1.7unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-506 · source CWE mapping

Embedded Malicious Code

Embedded Malicious Code represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.