future-scripts (npm) · Malicious Code
Affects future-scriptsSource GCVE Database
Malicious package : remove future-scripts and rotate any secrets on hosts that installed it.
Data as of 12 Nov 2026, 19:19 UTC
Malicious package
Published to npm · OSV MAL-2026-17418
What to do
Remove future-scripts 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 |
|---|---|---|
| npmfuture-scripts | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
On October 10, 2026 (local time), boom() calls localStorage.setItem('key', i) 100,000,000 times in a synchronous loop, potentially freezing a browser page. In version 0.0.2, the exported getCommonDateInRanges() calls boom() before input validation; the bundled source map confirms this path. Version 0.0.3 retains boom() as a separate export but no longer calls it from getCommonDateInRanges(), so an explicit call is required. Version 0.0.1 does not contain this routine. This is a static finding; actual victim impact was not observed. --- _-= Per source details. Do not edit below this line.=-_ ## Source: ghsa-malware (85a5edaae5c58b417dfd2c63bf8f2529bc3aa75784254950f457847fc7840561) 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 the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.