Vulnerability Database · npm · initial-path21 · Version
initial-path21 3.3.9
3.3.9 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 22/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
initial-path21 3.3.9 vulnerabilities
1 vulnerability cover initial-path21 3.3.9. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| Malicious Code Vulnerability in initial-path21 Package | N/A critical | No fix published | 18 Mar 2026 |
Looking for another version, or everything Vulert holds for initial-path21?
Questions
About initial-path21 3.3.9
Is initial-path21 3.3.9 vulnerable?
Yes. 1 vulnerability in the Vulert database cover initial-path21 3.3.9: 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 initial-path21 for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the initial-path21 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.