Threats / Prettier / CVE-2025-54313
CVE-2025-54313
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Prettier eslint-config-prettier vulnerability
eslint-config-prettier contains malicious code that executes during package installation, deploying node-gyp.dll malware on Windows systems.
Verdict
Today item — known-exploited.
Supply chain compromise in a widely-used npm package. Installation triggers execution of embedded malware, affecting developers and CI/CD pipelines. CWE-506 indicates intentional malicious code obfuscation.
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
6 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-01-22).
Probability (EPSS)
EPSS 0.04146 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Prettier, eslint-config-prettier. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-506 CWE-506.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
WeaknessCWE-506 · CWE-506
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
Compromise the eslint-config-prettier package repository to inject malicious install.js script.
Business
Development teams unknowingly install compromised dependency, introducing malware into build environments.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
Execute node-gyp.dll malware during npm install on Windows developer machines and CI/CD runners.
Business
Malware gains execution context within development infrastructure with potential access to source code and credentials.
3
Lateral reach — past segmentation narrative 3
Attacker
Establish persistence and exfiltrate sensitive data or inject backdoors into built artifacts.
Business
Compromised software builds propagate malware to end users; intellectual property and customer data at risk.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05