CVERadar
HIGH · CVSS 3.1 7.5CISA KEV · added 2026-01-22EPSS 5.13% (p92)Threat level 54

CVE-2025-54313: Prettier eslint-config-prettier Embedded Malicious Code Vulnerability

Prettier · eslint-config-prettier · NVD published 2025-07-19 · posted 2026-01-22 · last modified 2026-06-17

What it is

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.

WeaknessCWE-506
CVSS vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:N (source: [email protected])
CISA due date2026-02-12 (for US federal agencies under BOD; a good deadline for everyone)
ATT&CK tacticsn/a

Exploitation evidence

First exploit evidence seen: 2026-01-22 (earliest date across the sources below).

Exploited in the wild

  • CISA KEV: listed since 2026-01-22. Source

Public exploit code

GitHub proof-of-concept repositories below quality bar

2 public repositories from 2 accounts, first seen 2025-07-26.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: CISA KEV · nomi-sec/PoC-in-GitHub.

No ATT&CK techniques could be mapped or inferred for this CVE yet.

How to fix it

CISA required action

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. (source: CISA KEV)

Fixed versions

  • homarr homarr: upgrade to 1.30.0 or later (affected from 1.29.0)

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

Detection Generic guidance

    Response checklist Generic guidance

    1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
    2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
    3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
    4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

    Sources