Security researchers are essential in identifying vulnerabilities that may impact the Sei ecosystem. If you have discovered a security vulnerability in the Sei chain or any repository managed by Sei, we encourage you to notify us using one of the methods outlined below.
- Refrain from testing vulnerabilities on our publicly accessible environments, including but not limited to:
- Sei mainnet
pacific-1 - Sei frontend
- Sei public testnets
- Sei testnet frontend
- Avoid reporting security vulnerabilities through public channels, including GitHub issues
To privately report a security vulnerability, please choose one of the following options:
Send your detailed vulnerability report to [email protected].
Utilize GitHub's Private Vulnerability Reporting for confidential disclosure.
When reporting a vulnerability through either method, please include the following details to aid in our assessment:
- Type of vulnerability
- Description of the vulnerability
- Steps to reproduce the issue
- Impact of the issue
- Explanation on how an attacker could exploit it
- Initial Report: Submit the vulnerability via one of the above channels.
- Confirmation: We will confirm receipt of your report within 48 hours.
- Assessment: Our security team will evaluate the vulnerability and inform you of its severity and the estimated time frame for resolution.
- Resolution: Once fixed, you will be contacted to verify the solution.
- Public Disclosure: Details of the vulnerability may be publicly disclosed after ensuring it poses no further risk.
During the vulnerability disclosure process, we ask security researchers to keep vulnerabilities and communications around vulnerability submissions private and confidential until a patch is developed. Should a security issue require a network upgrade, additional time may be needed to raise a governance proposal and complete the upgrade.
During this time:
- Avoid exploiting any vulnerabilities you discover.
- Demonstrate good faith by not disrupting or degrading Sei's services.
For a feature request, e.g. module inclusion, please make a GitHub issue. Clearly state your use case and what value it will bring to other users or developers on Sei.
| Severity | Description |
|---|---|
| CRITICAL | Immediate threat to critical systems (e.g., chain halts, funds at risk) |
| HIGH | Significant impact on major functionality |
| MEDIUM | Impacts minor features or exposes non-sensitive data |
| LOW | Minimal impact |
For recommendations on how to improve this policy, either submit a pull request or email [email protected].