Malware in devplatform-spa-plugin-s3-router
Malware discovered in the npm package devplatform-spa-plugin-s3-router. Systems with this package installed 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
- devplatform-spa-plugin-s3-router
A malware incident was identified in the npm package devplatform-spa-plugin-s3-router, published as GitHub Advisory GHSA-h72c-g9pj-cr88 on August 5, 2026.\n\nAccording to the advisory, any computer with this package installed or running should be considered fully compromised. The malware grants outside entities full control of affected systems.\n\nImmediate action is required: all secrets and keys stored on affected computers must 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 initial compromise.
Indicators of compromise
- Packages
- devplatform-spa-plugin-s3-router
Remediation
- Immediately remove the devplatform-spa-plugin-s3-router package from all systems
- Rotate all secrets, API keys, and credentials stored on affected computers from a different, uncompromised system
- Conduct a full security audit and forensic analysis of any system that had this package installed
- Monitor affected systems for signs of persistent malware or unauthorized access
- Review and revoke any access tokens or credentials that may have been exposed
Sources
- GitHub Advisory GHSA-h72c-g9pj-cr88 · GitHub Advisory Database
Cite this entry
"Malware in devplatform-spa-plugin-s3-router." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 5, 2026; last updated August 5, 2026. https://supplychainattack.org/incident/malware-in-devplatform-spa-plugin-s3-router-kpm4h6
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 github-policy-bot (npm)
The npm package github-policy-bot contained malicious code that exfiltrated host identifiers and environment metadata during installation via a postinstall script. The package name shadowed a legitimate Google-owned repository and was authored under a placeholder account claiming security research purposes.
npmCompromised packageTyposquatting - containedcritical
Malicious code in crypto-javas (npm)
The npm package crypto-javas contains malicious code in its postinstall hook and main entrypoint that harvests environment variables (including CI secrets like AWS_*, GITHUB_TOKEN, NPM_TOKEN) and exfiltrates them to an attacker-controlled backend. The package is presented deceptively as @wizlabs/js-crypto with a placeholder repository.
npmCompromised packageTyposquatting - containedcritical
Malicious code in flydev (npm)
The npm package flydev contains malicious code designed to destroy Windows systems. The package masquerades as a utility but executes destructive operations including filesystem deletion, process termination, memory exhaustion, and fork bombs when invoked.
npmCompromised package - containedcritical
Malicious code in npm-wold (npm)
npm-wold@1.1.1 contains malicious code in its postinstall script that fetches remote JSON from a hardcoded endpoint and dynamically invokes attacker-controlled functions with attacker-supplied arguments, enabling code execution at install time.
npmCompromised package