GHSA-5j4v-g9j4-3f38: Malicious code in future-scripts (npm)
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Remove
Remove
npm/future-scriptsfrom your environment.Remove the package from any affected computer; removing it may not remove all malicious software resulting from its installation.
- Operational
Rotate all secrets and keys stored on any computer with this package installed or running, immediately and from a different computer.
Event History
Frequently Asked Questions
Which package versions have the browser-freezing behavior?
Version 0.0.2 calls boom() from getCommonDateInRanges() before input validation. Version 0.0.3 retains boom() but requires an explicit call, while version 0.0.1 does not contain this routine.
What conditions are needed to trigger the browser impact?
On October 10, 2026 local time, boom() performs 100,000,000 synchronous localStorage.setItem() calls. In version 0.0.2, invoking getCommonDateInRanges() reaches this code path; in version 0.0.3, an attacker or caller would need to explicitly invoke boom().
What should an organization do if this package was installed or executed?
Treat the affected computer as fully compromised. Remove the package and rotate all secrets and keys stored on that computer from a different computer, recognizing that package removal may not remove other malicious software.