lock-deadline-guard (npm) · Malicious Code
Affects lock-deadline-guardSource GCVE Database
Malicious package : remove lock-deadline-guard and rotate any secrets on hosts that installed it.
Data as of 14 Aug 2026, 16:47 UTC
Malicious package
Published to npm · OSV MAL-2026-14004
What to do
Remove lock-deadline-guard from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmlock-deadline-guard | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The npm package 'lock-deadline-guard' version 1.1.3 contains malicious code or depends on a package with malicious code. Any system with this package installed should be considered fully compromised, requiring immediate rotation of all secrets and keys from a different machine. Removal of the package alone may not eliminate all malicious software due to potential full system compromise.