Vulnerability Database · npm · normal-store · Version
normal-store 1.3.2
1.3.2 is affected by 1 vulnerability.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 1 High 0 Medium 0 Low 0 Unrated 0
-
Database updated 23/Oct/2026
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
normal-store 1.3.2 vulnerabilities
1 vulnerability cover normal-store 1.3.2. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| Critical Malicious Code Vulnerability in normal-store Package | N/A critical | No fix published | 24 Nov 2025 |
Looking for another version, or everything Vulert holds for normal-store?
Questions
About normal-store 1.3.2
Is normal-store 1.3.2 vulnerable?
Yes. 1 vulnerability in the Vulert database cover normal-store 1.3.2: 1 critical, 0 high, 0 medium and 0 low. Each entry above names the fixed version to move to.
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 normal-store for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the normal-store version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.