CVE-2025-54313
KEVPrettier eslint-config-prettier Embedded Malicious Code Vulnerability
Description
Prettier eslint-config-prettier contains an embedded malicious code vulnerability. Installing an affected package executes an install.js file that launches the node-gyp.dll malware on Windows.
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.
CVSS 3.1 vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:NPublishedJul 19, 2025
Last modifiedJun 17, 2026
Added to KEVJan 22, 2026
Remediation dueFeb 12, 2026
References
- github.com/prettier/eslint-config-prettier/issues/339Issue Tracking
- news.ycombinator.com/item?id=44608811Issue Tracking
- news.ycombinator.com/item?id=44609732Issue Tracking
- socket.dev/blog/npm-phishing-campaign-leads-to-prettier-tooling-packages-compromiseThird Party Advisory
- bleepingcomputer.com/news/security/popular-npm-linter-packages-hijacked-via-phishing-to-drop-malware/ExploitThird Party Advisory
- npmjs.com/package/eslint-config-prettier?activeTab=versionsProduct
- stepsecurity.io/blog/supply-chain-security-alert-eslint-config-prettier-package-shows-signs-of-compromiseExploitThird Party Advisory
- github.com/community-scripts/ProxmoxVE/discussions/6115Third Party Advisory
- endorlabs.com/learn/cve-2025-54313-eslint-config-prettier-compromise----high-severity-but-windows-onlyThird Party Advisory
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-54313US Government Resource
0 recent articles mention this CVE
68
Risk assessment · High
Actively exploited. Patch immediately.
- Exploitation
- Confirmed in the wild (CISA KEV)
- Federal remediation deadline
- Overdue by 257 days
- CVSS
- 7.5 HIGH
- EPSS (30-day exploit probability)
- 5.1% · top 8% of all CVEs
- Weakness
- CWE-506
- Attack vector
- Network, remotely reachable
- Preconditions
- No privileges and no user interaction
Recommended actions
- 1.Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
- 2.Treat as emergency change: patch or isolate internet-facing instances first.
- 3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
- 4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.
Assessment is derived automatically from the live signals above; verify against your own asset inventory.