Malware in vite-json-pwa
Malware was discovered in the npm package vite-json-pwa. Systems with this package installed or running are 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
- vite-json-pwa
The npm package vite-json-pwa was found to contain malware. According to the GitHub Advisory (GHSA-3f72-wf55-pqjc), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends that all secrets and keys stored on affected computers be rotated immediately 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 package installation, given the potential for full system compromise.\n\nUsers should treat any system that has run this package as potentially containing persistent malware and take appropriate incident response measures.
Indicators of compromise
- Packages
- vite-json-pwa
Remediation
- Immediately rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the vite-json-pwa package from all affected systems
- Perform a full security audit and malware scan of any system that had this package installed or running
- Consider the affected system(s) as potentially compromised and plan for full remediation or replacement
- Review access logs and audit trails for any unauthorized activity on affected systems
- Notify relevant stakeholders and security teams of the compromise
Sources
- GitHub Advisory GHSA-3f72-wf55-pqjc · GitHub Advisory Database
Cite this entry
"Malware in vite-json-pwa." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 8, 2026; last updated July 8, 2026. https://supplychainattack.org/incident/malware-in-vite-json-pwa-1vnucn
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 autbank-core (npm)
The npm package autbank-core contained malicious preinstall and postinstall lifecycle hooks that exfiltrated environment variables, credentials, and system information to a hardcoded webhook.site endpoint during installation.
npmCompromised package - resolvedcritical
Malicious code in adxaa (npm)
The npm package adxaa contained obfuscated malicious JavaScript designed to target users of a specific WordPress site. The payload exfiltrates session data, deletes accounts, and hijacks credentials via email overwrite and password reset.
npmCompromised package - resolvedcritical
Malicious code in upload-to-gcp (npm)
upload-to-gcp@3.2.1 (npm) contains malicious code in its postinstall script that exfiltrates host identifiers to an attacker-controlled endpoint. The package masquerades as a Google Cloud Platform utility but performs unauthorized telemetry collection at install time.
npmCompromised package - resolvedcritical
Malicious code in akamai-sensor (npm)
A malicious npm package named akamai-sensor impersonated Akamai's legitimate sensor_data anti-bot SDK. The package contained hidden JavaScript code concealed using invisible Unicode characters and implemented a dynamic command-and-control channel via a Google Calendar dead-drop, enabling arbitrary code execution on installation.
npmCompromised packageTyposquatting