Malicious code in node-fetch-utils (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (78aef0d64a7d761d2987d27aea462083425e5692475cd81332b7a3152c754308) On Windows, scripts/postinstall.js XOR-decodes a hardcoded C2 host (node22.lunes.host:3258), authenticates with a 5-minute rolling HMAC-SHA256 token, downloads encrypted Python marshal bytecode from /sync and /go, decrypts it with a sha256 keystream, writes a.dat blob and a Python launcher to %TEMP%, and spawns it detached/hidden via wscript.exe //B //nologo against a generated.vbs — with a code comment explicitly noting that this 'escapes npm job object'. The launcher and.vbs self-delete after spawn. The package.json also pulls a transitive dependency 'node-fetch-core' from an unpinned GitHub master-branch tarball owned by the same author, providing a second mutable auto-execution surface that bypasses registry review and can be swapped post-publish. The package name mimics the well-known node-fetch library, consistent with a typosquat lure delivering this payload. Multi-layer obfuscation (XOR-encoded host/port, HMAC time-window authentication, keystream-encrypted payload, marshal'd bytecode), explicit npm job-object evasion, and self-deleting launchers are operational malware tradecraft, not legitimate install scaffolding. ## Source: ghsa-malware (618e71900ba6c670ed38028718e5dc5db3147ada60e3c7f11a0a519d33a4e783) 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.
AI Analysis
Technical Summary
The node-fetch-utils npm package (versions 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.2.6, 1.2.7, and 1.3.0) contains malicious post-install scripts that XOR-decode a hardcoded C2 host, authenticate with a time-based HMAC-SHA256 token, download encrypted Python marshal bytecode, decrypt it, write it to temporary files, and execute it hidden via wscript.exe with self-deleting launchers. The package.json pulls a transitive dependency from an unpinned GitHub master branch tarball controlled by the same author, providing a mutable execution surface that bypasses npm registry review. The package name mimics the popular node-fetch library, consistent with typosquatting tactics. These behaviors constitute operational malware tradecraft rather than legitimate package functionality.
Potential Impact
Any system with this package installed or running should be considered fully compromised. The malware grants remote code execution capabilities to an attacker, potentially allowing full control over the affected system. All secrets and keys stored on the compromised system should be considered exposed and rotated immediately from a secure environment. Removing the package alone may not eliminate the malware due to its persistence mechanisms and post-install payload execution.
Mitigation Recommendations
No official patch or fix is currently available for this malicious package. The recommended mitigation is to immediately remove the node-fetch-utils package from all affected systems. Rotate all secrets and credentials that were stored or used on the compromised systems from a separate, secure environment. Conduct a thorough investigation and remediation of the affected hosts, as full compromise is likely. Monitor for any signs of persistence or additional malicious activity resulting from the installation of this package.
Malicious code in node-fetch-utils (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (78aef0d64a7d761d2987d27aea462083425e5692475cd81332b7a3152c754308) On Windows, scripts/postinstall.js XOR-decodes a hardcoded C2 host (node22.lunes.host:3258), authenticates with a 5-minute rolling HMAC-SHA256 token, downloads encrypted Python marshal bytecode from /sync and /go, decrypts it with a sha256 keystream, writes a.dat blob and a Python launcher to %TEMP%, and spawns it detached/hidden via wscript.exe //B //nologo against a generated.vbs — with a code comment explicitly noting that this 'escapes npm job object'. The launcher and.vbs self-delete after spawn. The package.json also pulls a transitive dependency 'node-fetch-core' from an unpinned GitHub master-branch tarball owned by the same author, providing a second mutable auto-execution surface that bypasses registry review and can be swapped post-publish. The package name mimics the well-known node-fetch library, consistent with a typosquat lure delivering this payload. Multi-layer obfuscation (XOR-encoded host/port, HMAC time-window authentication, keystream-encrypted payload, marshal'd bytecode), explicit npm job-object evasion, and self-deleting launchers are operational malware tradecraft, not legitimate install scaffolding. ## Source: ghsa-malware (618e71900ba6c670ed38028718e5dc5db3147ada60e3c7f11a0a519d33a4e783) 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
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 node-fetch-utils npm package (versions 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.2.6, 1.2.7, and 1.3.0) contains malicious post-install scripts that XOR-decode a hardcoded C2 host, authenticate with a time-based HMAC-SHA256 token, download encrypted Python marshal bytecode, decrypt it, write it to temporary files, and execute it hidden via wscript.exe with self-deleting launchers. The package.json pulls a transitive dependency from an unpinned GitHub master branch tarball controlled by the same author, providing a mutable execution surface that bypasses npm registry review. The package name mimics the popular node-fetch library, consistent with typosquatting tactics. These behaviors constitute operational malware tradecraft rather than legitimate package functionality.
Potential Impact
Any system with this package installed or running should be considered fully compromised. The malware grants remote code execution capabilities to an attacker, potentially allowing full control over the affected system. All secrets and keys stored on the compromised system should be considered exposed and rotated immediately from a secure environment. Removing the package alone may not eliminate the malware due to its persistence mechanisms and post-install payload execution.
Mitigation Recommendations
No official patch or fix is currently available for this malicious package. The recommended mitigation is to immediately remove the node-fetch-utils package from all affected systems. Rotate all secrets and credentials that were stored or used on the compromised systems from a separate, secure environment. Conduct a thorough investigation and remediation of the affected hosts, as full compromise is likely. Monitor for any signs of persistence or additional malicious activity resulting from the installation of this package.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-6271
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-4jfq-h5q8-g7hm"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a4f6c3d68715ace431589a9
Added to database: 07/09/2026, 09:39:09 UTC
Last enriched: 07/09/2026, 09:53:23 UTC
Last updated: 07/29/2026, 19:58:12 UTC
Views: 12
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.