Malware in fetch-page-assets
Malware was discovered in the npm package fetch-page-assets. Systems with this package installed or running should be considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- fetch-page-assets
The npm package fetch-page-assets was found to contain malware. According to the GitHub Advisory (GHSA-vxq2-vhm7-7mhq), any computer with this package installed or running should be considered fully compromised.\n\nImmediate action is required: all secrets and keys stored on affected computers should be rotated from a different, uncompromised system. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the compromise.\n\nThe advisory indicates that full control of affected systems may have been given to an outside entity, necessitating comprehensive security review and remediation beyond simple package removal.
Indicators of compromise
- Packages
- fetch-page-assets
Remediation
- Immediately rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the fetch-page-assets package from all affected systems
- Conduct a full security audit of any system that had this package installed
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical systems are involved
- Notify any services or systems that may have been accessed from the compromised computer
Sources
- GitHub Advisory GHSA-vxq2-vhm7-7mhq · GitHub Advisory Database
Cite this entry
"Malware in fetch-page-assets." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 24, 2026; last updated June 24, 2026. https://supplychainattack.org/incident/malware-in-fetch-page-assets-s66ff1
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in typescirpt-cli (npm)
The npm package typescirpt-cli (a typosquat of typescript-cli) contained malicious code in its postinstall script that downloads and executes a binary (main.exe) on Windows and WSL systems, and exfiltrates system metadata to a hardcoded IP address.
npmTyposquattingCompromised package - containedcritical
Malicious code in typescipt-core (npm)
The npm package typescipt-core (a typosquat of typescript) contained malicious postinstall code that downloads and executes a second-stage payload on Windows and WSL systems. The dropper exfiltrates host profile information to 193.70.34.101:20099 before fetching attacker-controlled executables.
npmCompromised packageTyposquatting - containedcritical
Malicious code in typesript-cli (npm)
The npm package 'typesript-cli' (a one-character typosquat of 'typescript') contains malicious code in its postinstall script that downloads and executes a Windows PE binary, and can cross the Linux/WSL sandbox boundary to execute payloads on the Windows host. The script also beacons to a hardcoded IP endpoint.
npmTyposquattingCompromised package - resolvedcritical
Malicious code in @mohamed_nowisar/depconf-canary-test (npm)
The npm package @mohamed_nowisar/depconf-canary-test contained malicious code in its preinstall hook that automatically collected and exfiltrated host and CI environment information to an attacker-controlled webhook endpoint without user consent.
npmCompromised package