Vulnerability Database · npm · failing-code · Version
failing-code 0.0.2
0.0.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
-
Released 21 Mar 2014
Licence non-standard
Also known from other sources 1
Newer releases 6
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
failing-code 0.0.2 vulnerabilities
1 vulnerability cover failing-code 0.0.2. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| Critical Malicious Code Vulnerability in failing-code Package | N/A critical | No fix published | 14 Aug 2025 |
Looking for another version, or everything Vulert holds for failing-code?
Questions
About failing-code 0.0.2
Is failing-code 0.0.2 vulnerable?
Yes. 1 vulnerability in the Vulert database cover failing-code 0.0.2: 1 critical, 0 high, 0 medium and 0 low. Each entry above names the fixed version to move to.
Is 0.0.2 the latest release of failing-code?
No. 0.0.2 was published 21 Mar 2014, 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 failing-code for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the failing-code version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.