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