Malware in sight-bind
Malware discovered in the npm package sight-bind. 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 sight-bind installed or running is considered fully compromised
- Ecosystems
- Attack vectors
- Affected entities
- sight-bind
The npm package sight-bind has been identified as containing malware. According to the GitHub advisory (GHSA-v3x8-hfcr-q8p2), any computer that has this package installed or running should be considered fully compromised.\n\nImmediate action is required: all secrets and keys stored on affected computers should be rotated immediately from a different, unaffected computer. The package should be removed, though there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the package installation.\n\nGiven the critical nature of the compromise, systems should be treated as potentially having given full control to an outside entity.
Indicators of compromise
- Packages
- sight-bind
Remediation
- Immediately rotate all secrets and keys from a different, unaffected computer
- Remove the sight-bind package from all affected systems
- Conduct a full security audit of any system that had sight-bind installed
- Monitor affected systems for signs of unauthorized access or persistence mechanisms
- Consider full system reimaging if secrets cannot be fully rotated or if persistence is suspected
Sources
- GitHub Advisory GHSA-v3x8-hfcr-q8p2 · GitHub Advisory Database
Cite this entry
"Malware in sight-bind." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 14, 2026; last updated July 14, 2026. https://supplychainattack.org/incident/malware-in-sight-bind-fgk5ts
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