MalwarePublished 11 Aug 2026Updated 12 Aug 2026

fetch-runtime (npm) · Malicious Code

Affects fetch-runtimeSource GCVE Database

Malicious package : remove fetch-runtime and rotate any secrets on hosts that installed it.

Data as of 12 Aug 2026, 16:47 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-13763

What to do

Remove fetch-runtime 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
npmfetch-runtime	Affected 1.2.0 – 1.5.0 4 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The 'fetch-runtime' npm package is a malicious rebranded copy of the legitimate 'make-fetch-happen' library. It includes inert base64-encoded strings exported but not used within the package, suggesting a possible two-stage attack design. Although the package itself does not perform malicious actions upon installation or import, its presence indicates a fully compromised system. Immediate removal and secret/key rotation are strongly advised, but full remediation may require a complete system rebuild due to potential persistent compromise.

Impact

Any system with the 'fetch-runtime' package installed should be considered fully compromised. Attackers may have gained complete control, and all stored secrets and keys on that system are at risk. Removing the package alone does not guarantee removal of all malicious artifacts or backdoors, implying a high risk of persistent compromise.

Defensive guidance

Remove the 'fetch-runtime' package immediately. Rotate all secrets and credentials from a different, uncompromised system. Due to the likelihood of full system compromise, consider rebuilding the affected system from a known clean state.

Summary

The 'fetch-runtime' package on npm is a malicious clone of the 'make-fetch-happen' library. It exports two constants containing opaque base64-encoded strings that are never decoded or executed within the package, indicating a potential two-stage attack vector where another component might use these exports as payload or keys. The package does not execute network I/O or lifecycle scripts by itself, so installing or requiring it alone does not directly cause exfiltration or remote code execution. However, the presence of this package on a system is considered a strong indicator of full system compromise, as per the GHSA advisory, and all secrets on the affected system should be rotated from a clean environment.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Aug 2026, 16:47 UTC

Technical details

References

Community reviews