Malicious code in fetch-runtime (npm)
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.
AI Analysis
Technical 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.
Potential 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.
Mitigation Recommendations
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. There is no official patch or fix available for this malicious package; remediation relies on removal and secret rotation.
Malicious code in fetch-runtime (npm)
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.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
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.
Potential 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. There is no official patch or fix available for this malicious package; remediation relies on removal and secret rotation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-13763
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-3hqj-592v-g33j"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a7c9b46bf8831d539cdd160
Added to database: 08/12/2026, 16:11:50 UTC
Last enriched: 08/12/2026, 16:47:41 UTC
Last updated: 08/12/2026, 16:47:41 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.