single-flight-lock (npm) · Malicious Code
Affects single-flight-lockSource GCVE Database
Malicious package : remove single-flight-lock and rotate any secrets on hosts that installed it.
Data as of 14 Aug 2026, 16:45 UTC
Malicious package
Published to npm · OSV MAL-2026-14012
What to do
Remove single-flight-lock 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 |
|---|---|---|
| npmsingle-flight-lock | 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 'single-flight-lock' version 1.0.0 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. Removing the package alone may not eliminate all malicious software introduced by it.