Malware in sea-bound-siren
The npm package sea-bound-siren contained malware that fully compromised any system where it was installed or running. The package has been identified and removed from distribution.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- sea-bound-siren
The npm package sea-bound-siren was found to contain malware. According to the GitHub Advisory, any computer with this package installed or running should be considered fully compromised, with potential for complete system takeover by an outside entity.\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.\n\nThe package has been flagged in the GitHub Advisory database as of June 12, 2026.
Indicators of compromise
- Packages
- sea-bound-siren
Remediation
- Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
- Remove the sea-bound-siren package from all affected systems
- Conduct a full security audit and forensic analysis of any system that had the package installed
- Monitor affected systems for signs of persistent malware or unauthorized access
- Consider the affected system(s) potentially compromised and plan for full rebuild if critical infrastructure
Sources
- GitHub Advisory GHSA-cp5x-35vp-rj7j · GitHub Advisory Database
Cite this entry
"Malware in sea-bound-siren." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 12, 2026; last updated June 12, 2026. https://supplychainattack.org/incident/malware-in-sea-bound-siren-1mzbg1
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- activecritical
Malware in chain-manager
Malware discovered in the npm package chain-manager. Systems with this package installed or running are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malicious code in @finxsecdemo/utils (npm)
The npm package @finxsecdemo/utils version 1.0.2 was identified as malicious by the OpenSSF Package Analysis project. The package communicates with a domain associated with malicious activity.
npmCompromised package - containedcritical
Malware in @bowozzz/baileys
The npm package @bowozzz/baileys contained malware that grants full system compromise to attackers. Any computer with this package installed should be considered fully compromised and all secrets and keys rotated immediately from a different machine.
npmCompromised package - containedcritical
Malicious code in blots (npm)
The npm package 'blots' version 2.1.0 was identified by the OpenSSF Package Analysis project as containing malicious code that executes commands associated with malicious behavior. The package has been flagged in the OpenSSF malicious packages database.
npmCompromised package