Vulnerability Database · npm · eslint-config-prettier · Version
eslint-config-prettier 2.3.0
2.3.0 is affected by 1 vulnerability.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 10.1.8.
Critical 1 High 0 Medium 0 Low 0 Unrated 0
-
Released 30 Jun 2017
Licence MIT
Also known from other sources 0
Newer releases 85
Database updated 23/Oct/2026
Release and licence data published by the npm registry. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
eslint-config-prettier 2.3.0 vulnerabilities
1 vulnerability cover eslint-config-prettier 2.3.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| Critical Malware Threat in eslint-config-prettier: Windows-Based Malware Installation | N/A critical | No fix published | 21 Jul 2025 |
Looking for another version, or everything Vulert holds for eslint-config-prettier?
Questions
About eslint-config-prettier 2.3.0
Is eslint-config-prettier 2.3.0 vulnerable?
Yes. 1 vulnerability in the Vulert database cover eslint-config-prettier 2.3.0: 1 critical, 0 high, 0 medium and 0 low. The upgrade Vulert recommends is 10.1.8, and each entry above names the fixed version to move to.
Which version of eslint-config-prettier should I use instead of 2.3.0?
10.1.8 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 2.3.0 the latest release of eslint-config-prettier?
No. 2.3.0 was published 30 Jun 2017, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
What does a malicious-package vulnerability mean?
It means the published package itself contained hostile code — a backdoor, a credential stealer or similar — rather than only a bug. Registries remove such packages once they are confirmed, so treat any application that resolved an affected version as compromised and rotate the credentials it could reach.
How do I monitor eslint-config-prettier for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the eslint-config-prettier version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.