Security Vulnerability Disclosure
Reporting Security Issues
If you discover a security vulnerability in Trezor Suite or Connect:Contact Security Team
Email your findings to [email protected]Include:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
Wait for Response
The security team will:
- Acknowledge receipt within 48 hours
- Assess the severity
- Determine fix timeline
- Keep you informed of progress
Responsible Disclosure
Please allow time for:
- Investigation and validation
- Development of fix
- Testing and deployment
- Public disclosure coordination
For more details, see the disclosure section on Trezor.io.
Security Best Practices
For Developers
Never Request Private Keys
Never Request Private Keys
Critical Rule: Private keys must NEVER leave the Trezor device.Why it matters:
- Trezor’s security model relies on keys never leaving device
- Exporting keys defeats the purpose of hardware security
- If you need to sign something, use the appropriate signing method
Verify Addresses on Device
Verify Addresses on Device
Always show addresses on the device display:Why it matters:
- Protects against malware showing fake addresses
- User can verify on trusted device screen
- Only source of truth is the device display
Use HTTPS in Production
Use HTTPS in Production
Always serve your application over HTTPS:Why it matters:
- Prevents man-in-the-middle attacks
- Protects user data in transit
- Required for WebUSB API in browsers
Validate Transaction Data
Validate Transaction Data
Always validate transaction parameters:
Implement Proper Error Handling
Implement Proper Error Handling
Handle errors securely without leaking information:
Sanitize User Input
Sanitize User Input
Always sanitize and validate user input:
For Users
Verify Device Display
Verify Device Display
Always verify critical information on your Trezor device screen:
- Receiving addresses
- Transaction amounts
- Transaction recipients
- Contract interactions
Use Official Sources
Use Official Sources
Only download Suite from official sources:
- Website: trezor.io/start
- Web App: suite.trezor.io
- GitHub: github.com/trezor/trezor-suite
- HTTPS connection
- Valid SSL certificate
- Correct domain name
Verify Downloads
Verify Downloads
For desktop applications, verify signatures:Windows:
- Check digital signature of .exe file
- Verify signer: SatoshiLabs
- Check code signature
- Verify developer: SatoshiLabs
- Verify GPG signature
- Check SHA256 hash
Keep Software Updated
Keep Software Updated
Always use the latest versions:
- Device Firmware: Update when prompted
- Trezor Suite: Enable auto-updates
- Browser: Use latest version
- Security patches
- New features
- Bug fixes
Secure Your Recovery Seed
Secure Your Recovery Seed
Your recovery seed is the master key:DO:
- Write it on the provided card
- Store in a safe location
- Consider metal backup for fire/water resistance
- Use Shamir Backup for advanced security
- Store digitally (photos, files, cloud)
- Share with anyone
- Enter into computer or phone
- Store with your Trezor device
Security Features
Device Security
Hardware Isolation
Private keys never leave the device. All signing happens in the secure element.
PIN Protection
Device is locked with PIN. Wipes after multiple failed attempts.
Passphrase Support
Additional layer of security through BIP39 passphrase.
Screen Verification
All critical data displayed on trusted device screen.
Software Security
Open Source
All code is open source and auditable on GitHub.
Encrypted Communication
All device communication is encrypted end-to-end.
No Data Collection
Private keys and transaction details never leave your device.
Regular Audits
Regular security audits by independent firms.
License and Usage
The Trezor Suite monorepo is licensed under the TREZOR REFERENCE SOURCE LICENSE (T-RSL).Key Points
Reference Use
Reference Use
You may use the software within your company as a reference for:
- Debugging your products
- Maintaining your products
- Enhancing interoperability with Trezor
- Read-only use
- Cannot distribute outside your company
- Reference purposes only
Copyright Grant
Copyright Grant
Non-transferable, non-exclusive, worldwide, royalty-free copyright license to reproduce the software for reference use.
Patent Grant
Patent Grant
Non-transferable, non-exclusive, worldwide, royalty-free patent license for reference use.
Limitations
Limitations
- No trademark license
- Software is “as-is” with no warranties
- Patent litigation terminates license
Security Resources
Report Vulnerability
Contact security team
Security Center
Trezor security information
Best Practices
Development best practices
GitHub Security
GitHub security policy
Security is a shared responsibility. Developers should follow best practices, and users should verify all critical operations on their device screen.