CVE-2025-54313 — Prettier eslint-config-prettier Embedded Malicious Code Vulnerability
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Confirmed exploitation (CISA KEV)+35
- Public exploit/PoC (github)+6
- EPSS 4.9% (30-day exploitation probability)+14
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Npm Eslint-config-prettier: fixed in version 8.10.2 — github.com (GitHub Security Advisories)
- Npm Eslint-config-prettier: fixed in version 9.1.2 — github.com (GitHub Security Advisories)
- Npm Eslint-config-prettier: fixed in version 10.1.8 — github.com (GitHub Security Advisories)
- Npm Eslint-plugin-prettier: fixed in version 4.2.4 — github.com (GitHub Security Advisories)
- Npm Synckit: fixed in version 0.11.10 — github.com (GitHub Security Advisories)
- Npm @pkgr/core: fixed in version 0.2.9 — github.com (GitHub Security Advisories)
- Npm Napi-postinstall: fixed in version 0.3.2 — github.com (GitHub Security Advisories)
- Npm Got-fetch: fixed in version 6.0.0 — github.com (GitHub Security Advisories)
CISA required action CISA
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
US federal deadline: Feb 12, 2026 — passed 245 day(s) ago
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Alexghr Got-fetch, Homarr Homarr, Prettier Eslint-config-prettier…).
- Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- Apply the fixed version or the patch documented under Remediation.
- EPSS ahead of 92% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Alexghr | Got-fetch | version 5.1.1version 5.1.2 | Vulnerable | NIST National Vulnerability Database |
| Homarr | Homarr | ≥ 1.29.0 and < 1.30.0 | Vulnerable | NIST National Vulnerability Database |
| Prettier | Eslint-config-prettier | version 9.1.1version 10.1.6version 10.1.7version 8.10.1 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Prettier | Eslint-config-prettier | version 8.10.1version 9.1.1version 10.1.6version 10.1.7 | Vulnerable | NIST National Vulnerability Database |
| Prettier | Eslint-plugin-prettier | version 4.2.2version 4.2.3 | Vulnerable | NIST National Vulnerability Database |
| Un-ts | Napi-postinstall | version 0.3.1 | Vulnerable | NIST National Vulnerability Database |
| Un-ts | Pkgr/core | version 0.2.8 | Vulnerable | NIST National Vulnerability Database |
| Un-ts | Synckit | version 0.11.9 | Vulnerable | NIST National Vulnerability Database |
| Npm | @pkgr/core | version 0.2.8 | Vulnerable | GitHub Security Advisories |
| Npm | Eslint-config-prettier | version 8.10.1version 9.1.1≥ 10.1.6 and ≤ 10.1.7 | Vulnerable | GitHub Security Advisories |
| Npm | Eslint-plugin-prettier | ≥ 4.2.2 and ≤ 4.2.3 | Vulnerable | GitHub Security Advisories |
| Npm | Got-fetch | ≥ 5.1.11 and ≤ 5.1.12 | Vulnerable | GitHub Security Advisories |
| Npm | Napi-postinstall | version 0.3.1 | Vulnerable | GitHub Security Advisories |
| Npm | Synckit | version 0.11.9 | Vulnerable | GitHub Security Advisories |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.5 | CVSS 3.1 | High | 2.2 | 4.7 | cve@mitre.org via NIST National Vulnerability Database |
| 7.5 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 7.5 | CVSS 3.1 | High | — | — | mitre via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:N (score shown at the top: cve@mitre.org) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CISA KEV details CISA
CISA lists a CVE once it has evidence of exploitation against real targets.
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.
Public exploits, PoCs and detection templates
Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.
Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.
EPSS over time FIRST
Oct 12, 2026 → Oct 14, 2026 · 3 reading(s) · max 4.93%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Hunt retroactively in logs from before Jan 22, 2026 (KEV listing): exploitation may have started earlier.
Timeline
What happened to this CVE, newest first.
- 2026
- Fix documented
- Affected products added · npm/eslint-config-prettier, npm/eslint-plugin-prettier, npm/synckit, npm/@pkgr/core, npm/napi-postinstall, npm/got-fetch
- Affected products added · prettier/eslint-config-prettier, prettier/eslint-plugin-prettier, un-ts/synckit, un-ts/pkgr/core, alexghr/got-fetch, un-
- Source status changed · Published → Analyzed
- Record published
- Affected products added · prettier/eslint-config-prettier
- CVSS changed · 7.5
- Source status changed · → Published
- SSVC assessment updated
- Added to CISA KEV (detected)
- Record created in this database
- Added to CISA KEV catalog
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 3× References added · Oct 13, 2026 – Oct 13, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
20 on the record
- www.cisa.gov/known-exploited-vulnerabilities-catalog
- news.ycombinator.com/item
- news.ycombinator.com/item
- github.com/prettier/eslint-config-prettier/commit/9b0b0a47ec28a7a83cf65e8436a877
- github.com/community-scripts/ProxmoxVE/discussions/6115
- socket.dev/blog/npm-phishing-campaign-leads-to-prettier-tooling-packages-comprom
- github.com/un-ts/pkgr/commit/e1420c99e44d8a2ae949381f9fbe1af5ba9cb1dd
- secure.software/npm/packages/got-fetch
- www.stepsecurity.io/blog/supply-chain-security-alert-eslint-config-prettier-package-shows
- github.com/un-ts/synckit/commit/8f2ee32d4f75736a1c8d7e1101190a71e48909e4
- www.bleepingcomputer.com/news/security/popular-npm-linter-packages-hijacked-via-phishing-to-dr
- github.com/prettier/eslint-config-prettier/issues/339
- github.com/prettier/eslint-plugin-prettier/commit/ec39dd4400f10c52d10cd991c10fa8
- github.com/un-ts/napi-postinstall/commit/38b4e95cf554e2549b9e1e2c4ff6bff4da9a65f
- www.endorlabs.com/learn/cve-2025-54313-eslint-config-prettier-compromise----high-severi
- www.bleepingcomputer.com/news/security/popular-npm-linter-packages-hijacked-via-phishing-to-dr
- www.npmjs.com/package/eslint-config-prettier
- nvd.nist.gov/vuln/detail/CVE-2025-54313
- checkmarx.com/zero-post/supply-chain-phishing-campaign-drops-more-malware-into-npm-
- github.com/advisories/GHSA-f29h-pxvx-f335
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-32602 Homarr has a Race Condition in Invite Token Registration (TOCTOU) Apr 6, 2026
- High CVE-2026-33510 DOM-Based XSS in Homarr /auth/login Redirect Apr 6, 2026
- High CVE-2026-27796 Homarr: Unauthenticated Information Disclosure (Integration Metadata Leak) Mar 7, 2026
- Medium CVE-2026-27797 Homarr: Unauthenticated SSRF in rssFeed.ts Mar 7, 2026
- Medium CVE-2026-25123 Homarr affected by Unauthenticated SSRF / Port-Scan Primitive via widget.app.ping Feb 6, 2026
- Critical CVE-2025-67493 Homarr: missing input sanitization and possible privilege escalation through ldap search query injection Dec 17, 2025
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-54313 is "Prettier eslint-config-prettier Embedded Malicious Code Vulnerability", rated High. It affects Got-fetch (Alexghr); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 7.5 describes technical severity. EPSS 4.93% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.