lock-deadline-guard
Ecosystem: npm
Downloads:
- 0CriticalAffects 0 versions
- 0HighAffects 0 versions
- 0MediumAffects 0 versions
- 0ModerateAffects 0 versions
- 0LowAffects 0 versions
0vulnerabilities
- Critical0 (0.0%)
- High0 (0.0%)
- Medium0 (0.0%)
- Moderate0 (0.0%)
- Low0 (0.0%)
Monthly breakdown
- 0 vulnerabilities
- Critical: 0
- High: 0
- Medium: 0
- Moderate: 0
- Low: 0
Vulnerabilities (1)
Known vulnerabilities affecting lock-deadline-guard, based on data from OSV.
| ID | Severity | Summary | Affected versions | Published | Source |
|---|---|---|---|---|---|
| MAL-2026-14004 | Unknown | Malicious code in lock-deadline-guard (npm)--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (5d91ecfa280d3545a23564aca4ee8787aae8cf03a44a3133ffb54b21184f7d13) The package was found to contain malicious code or consuming dependency that contains malicious code ## Source: ghsa-malware (4cf24e2f382969e13e72788ccbaf5c82db07ed0e047c45ea2649f6e6cc3c23d8) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of |
| OSV (opens in a new tab) |
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (5d91ecfa280d3545a23564aca4ee8787aae8cf03a44a3133ffb54b21184f7d13) The package was found to contain malicious code or consuming dependency that contains malicious code ## Source: ghsa-malware (4cf24e2f382969e13e72788ccbaf5c82db07ed0e047c45ea2649f6e6cc3c23d8) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of