Malware in paraglide-js
Malware was discovered in the paraglide-js npm package. Systems with the package installed are considered fully compromised and require immediate remediation including secret rotation and package removal.
- Disclosed
- Last updated
- Blast radius
- Any system with paraglide-js installed or running
- Ecosystems
- Attack vectors
- Affected entities
- paraglide-js
A critical malware incident was identified in the paraglide-js npm package. According to the GitHub Advisory (GHSA-433p-gj42-fh44), 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 malicious 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 initial compromise, given that the attacker may have gained full control of the system.\n\nAffected users should treat their systems as potentially fully compromised and take appropriate incident response measures.
Indicators of compromise
- Packages
- paraglide-js
Remediation
- Immediately rotate all secrets and keys from a different, uncompromised computer
- Remove the paraglide-js package from all affected systems
- Conduct a full security audit and forensic analysis of affected systems
- Monitor for signs of unauthorized access or persistence mechanisms
- Review system logs for suspicious activity during the period the malicious package was installed
- Consider full system reimaging if compromise is confirmed
Sources
- GitHub Advisory GHSA-433p-gj42-fh44 · GitHub Advisory Database
Cite this entry
"Malware in paraglide-js." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 31, 2026; last updated July 31, 2026. https://supplychainattack.org/incident/malware-in-paraglide-js-rl9sxw
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in @404c3s4r/lodash
Malware was discovered in the npm package @404c3s4r/lodash. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malware in ai-backup-script
The npm package ai-backup-script contained malware that provided full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised.
npmCompromised package - activecritical
Malware in smart-npv-mcp
The npm package smart-npv-mcp contains malware that grants full control of affected systems. Any computer with this package installed or running should be considered fully compromised.
npmCompromised package - containedcritical
Malware in polyprompt
Malware was discovered in the npm package polyprompt, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.
npmCompromised package