Vulnerability Database · npm · angular2-security · Version
angular2-security 0.0.1-security
0.0.1-security 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
-
Released 16 Aug 2016
Status latest release
Licence ISC
Also known from other sources 1
Newer releases 1
Database updated 22/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
angular2-security 0.0.1-security vulnerabilities
1 vulnerability cover angular2-security 0.0.1-security. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| Malicious Code Detected in angular2-security Package | N/A critical | No fix published | 14 Aug 2025 |
Looking for another version, or everything Vulert holds for angular2-security?
Questions
About angular2-security 0.0.1-security
Is angular2-security 0.0.1-security vulnerable?
Yes. 1 vulnerability in the Vulert database cover angular2-security 0.0.1-security: 1 critical, 0 high, 0 medium and 0 low. Each entry above names the fixed version to move to.
Is 0.0.1-security the latest release of angular2-security?
Yes. 0.0.1-security is the current release, published 16 Aug 2016. Staying on the current line is what keeps you inside the publisher's fixes.
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 angular2-security for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the angular2-security version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.