Malware in wastu
The npm package wastu was found to contain malware that grants full system compromise to attackers. Any system with this package installed or running should be considered fully compromised and all secrets and keys rotated immediately from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- wastunpm package containing malware
The npm package wastu was identified as containing malware. According to the GitHub Advisory (GHSA-jwr5-mf48-j5vg), any computer that has 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 initial compromise, given that the attacker may have gained full control of the system.\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
- wastu
Remediation
- Immediately remove the wastu package from all systems
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Assume full system compromise and perform forensic analysis or rebuild affected systems
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Monitor for any unauthorized access to accounts or services that may have been compromised
Sources
- GitHub Advisory GHSA-jwr5-mf48-j5vg · GitHub Advisory Database
Cite this entry
"Malware in wastu." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 30, 2026; last updated July 30, 2026. https://supplychainattack.org/incident/malware-in-wastu-1ov65t
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 spectral-wraith
Malware was discovered in the npm package spectral-wraith. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.
npmCompromised package - activecritical
Malware in @spectraltest/loglevel
Malware discovered in the npm package @spectraltest/loglevel. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - resolvedcritical
Malware in ag-grid-boost
Malware was discovered in the npm package ag-grid-boost. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - activecritical
Malware in lodash-ex
Malware discovered in the npm package lodash-ex. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package