Which versions of future-scripts are malicious?

The following npm versions of future-scripts are flagged malicious: 0.0.2, 0.0.3. Treat any of these as compromised.

How do I remediate future-scripts if I installed it?

Remove future-scripts from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed future-scripts — how do I know if it already compromised me?

If future-scripts was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find future-scripts across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for future-scripts (2 malicious versions).

Malicious package

future-scriptsnpm

Advisory published Sep 30, 2026Updated Oct 1, 2026

future-scripts is a confirmed malicious npm package (MAL-2026-17418) that executes malicious code on install (malicious versions 0.0.2, 0.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in future-scripts (npm)

MAL-2026-17418

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall future-scripts

What this malware does

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.

Malicious versions

2 flagged

0.0.20.0.3

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for future-scripts (2 malicious versions).
If you installed it — respond
Remove future-scripts from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If future-scripts was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. future-scripts on npm has been identified as a malicious package (versions 0.0.2, 0.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

ESTsecurity · finder

Detect & block this

O3 blocks future-scripts-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database