Malware in stargateproxyserv
The npm package stargateproxyserv was found to contain malware, resulting in full system compromise of any computer with the package installed or running. All affected systems 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
- stargateproxyserv
The npm package stargateproxyserv was identified as containing malware. According to the GitHub Advisory (GHSA-h7c2-w78r-3m98), 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, unaffected computer. While the package should be removed, the advisory notes that because full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from the installation.\n\nThis represents a critical supply chain attack through a compromised npm package with the potential to affect all systems where it was deployed.
Indicators of compromise
- Packages
- stargateproxyserv
Remediation
- Immediately isolate any computer with stargateproxyserv installed from the network
- Rotate all secrets, API keys, credentials, and cryptographic keys from a different, unaffected computer
- Remove the stargateproxyserv package from all affected systems
- Conduct a full forensic analysis of affected systems to identify any additional malicious software installed
- Review all access logs and audit trails for the period the package was installed
- Consider full system reimaging if the package was installed on critical infrastructure or systems with access to sensitive data
Sources
- GitHub Advisory GHSA-h7c2-w78r-3m98 · GitHub Advisory Database
Cite this entry
"Malware in stargateproxyserv." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 27, 2026; last updated July 27, 2026. https://supplychainattack.org/incident/malware-in-stargateproxyserv-ebd4as
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 test2221 (npm)
The npm package test2221 version 2.2.4 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.
npmCompromised package - containedcritical
Malware in n8n-nodes-trust-me-im-totally-safe
Malware was discovered in the npm package n8n-nodes-trust-me-im-totally-safe, 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 - activecritical
Malware in litespeed-cache
Malware discovered in the npm package litespeed-cache. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.
npmCompromised package - containedcritical
Malware in open-worker-cli
Malware was discovered in the npm package open-worker-cli. 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