What is CVE-2025-54313?

CVE-2025-54313 is Prettier eslint-config-prettier Embedded Malicious Code Vulnerability. The supplied enrichment data classifies it as Unclassified mapped to CWE-506 CWE-506.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

3 public PoC repositories reported; 2 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2025-54313 using CVSS 7.5, EPSS 4%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

Publicly linked actor or ransomware signals in the supplied enrichment data: White Bear (), APT 28 (), TAG-28 (), Roaming Tiger (). Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVhighpublic exploit

CVE-2025-54313

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

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2025-54313 in CISA KEV with 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.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

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.

Published Jul 19, 2025Updated Jun 17, 2026Sources: NVD, prettier (CNA), CISA, FIRST EPSS, Red Hat (VEX), SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Jan 22, 2026

EPSS

ahead of 91% of scored CVEs

Affects

prettier

4 products listed

CVSS base

7.5

high

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

can an attacker script all four kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade eslint-config-prettier to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

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.

Federal deadline Feb 12, 2026 — passed 221 days ago

Red Hat VEX · CVE-2025-54313

fixed0affected0not affected122

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
prettier	eslint-config-prettier	8.10.1	Vulnerable
prettier	eslint-config-prettier	9.1.1	Vulnerable
prettier	eslint-config-prettier	10.1.6	Vulnerable
prettier	eslint-config-prettier	10.1.7	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

None

Confidentiality

Low

Integrity

High

Scope

Changed

Attack Complexity

High

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
7.5	CVSS 3.1	high	2.2	4.7	MITRE (CNA), prettier (CNA), Red Hat (VEX)

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

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-506 · Embedded Malicious Code

Execute Unauthorized Code or Commands::

Mitigation: Remove the malicious code and start an effort to ensure that no more malicious code exists. This may require a detailed review of all code, as it is possible to hide a serious attack in only one or two lines of code. These lines may be located almost anywhere in an application and may have been intentionally obfuscated by the attacker.::

Weakness & attack patterns

CWE-506

Inferred from the weakness class — not observed against this CVE.

T1195.001Supply Chain Compromise: Compromise Software Dependencies and Development Tools
T1195.002Supply Chain Compromise: Compromise Software Supply Chain
T1027.009Obfuscated Files or Information: Embedded Payloads

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Jan 22, 2026

Federal deadline

Feb 12, 2026

passed 221 days ago

Ransomware use

Unknown

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 date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

2 of the 3 sampled are weaponized

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable eslint-config-prettier.
Monitor for scanner or exploit-pattern traffic after 3 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

Groups associated with this CVE

Groups reported in connection with this vulnerability. A reported association, not a confirmed observation of that group using it — and not scoped to any sector or campaign.

White BearAPT 28TAG-28Roaming Tiger

ip89.144.31.1837
URLhaus Feeds · Dec 7, 2025
hashaa0d3859d6633b62bccfb69017d33a8979a3be1f3f0a5a4bf6960d6c73d4112199
Computer Incident Response Center Luxembourg (CIRCL) · Oct 6, 2025
hash6f746388853178a3b4c2c91a6bd98438fb59e760caa273a8d6a4c03936498c39100
AlienVault OTX Feeds · Jan 20, 2026
hash6fd538e4a8e3493dda6f9fcdc96e814bdd14f3e2ef8aa46f0143bff34b882c1b99
Computer Incident Response Center Luxembourg (CIRCL) · Oct 3, 2025
hash23094d64721a279c0ce637584b87d6f199
SOCRadar Threat Exchange Services · Oct 7, 2025

5 more indicators on this CVEShowing 5 of 10 · Hashes, addresses and domains from a live threat exchangeUnlock free

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 7.5 (AV:N)
Jun 17, 2026 · NVD
Added to CISA KEV catalog
Jan 22, 2026 · CISA
2025
Bulletin released on NIST.
Jul 23, 2025 · SOCRadar CTI
Bulletin released on NIST.
Jul 20, 2025 · SOCRadar CTI
Initial · CVE published
Jul 19, 2025 · NVD

Source activity

Readings a source repeats on a schedule, counted rather than listed.

8×SvrsJul 20, 2025 – Feb 19, 2026 · SOCRadar CTI
7×TweetsJul 25, 2025 – Mar 17, 2026 · SOCRadar CTI
7×ModifiedJul 20, 2025 – Jan 24, 2026 · SOCRadar CTI
3×Github ReposJul 26, 2025 – Sep 22, 2025 · SOCRadar CTI
1×1 time mentioned on 1 Telegram channelJan 25, 2026 · SOCRadar CTI
1×CVE appeared in the Cve Trends.Jan 24, 2026 · SOCRadar CTI

References

15 on the record

github.com/prettier/eslint-config-prettier/issues/339
Issue Tracking, NIST
news.ycombinator.com/item?id=44608811
Issue Tracking, NIST
news.ycombinator.com/item?id=44609732
Issue Tracking, NIST
socket.dev/blog/npm-phishing-campaign-leads-to-prettier-tooling-packages-compromise
Third Party Advisory, NIST
www.bleepingcomputer.com/news/security/popular-npm-linter-packages-hijacked-via-phishing-to-drop-malware/
Exploit, Third Party Advisory, NIST
www.npmjs.com/package/eslint-config-prettier?activeTab=versions
Product, NIST, GITHUB, Vendor Advisory
www.stepsecurity.io/blog/supply-chain-security-alert-eslint-config-prettier-package-shows-signs-of-compromise
Exploit, Third Party Advisory, NIST
github.com/community-scripts/ProxmoxVE/discussions/6115
Third Party Advisory, NIST

Coverage

13 stories from the feeds we poll

8 more reports on this CVEShowing 5 of 13 · Vendor research and security press coverageUnlock free

Elsewhere on this site

prettierevery CVE for this vendor
January 2026what else CISA listed
Unclassifiedsame class
CWE-506other pages naming this weakness

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.

Only the 5 indicator(s) reported for this CVE are available; no packet-level or host-forensic 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 record1

What should defenders know first?

CVE-2025-54313 is Prettier eslint-config-prettier Embedded Malicious Code Vulnerability, a high vulnerability affecting eslint-config-prettier from prettier. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 3 public PoC repositories reported; 2 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7.5 describes technical severity, while EPSS 4% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.