Incident type
OTHER
30% confidence
Severity score
LOW — 0/100
Incident does not exhibit high-risk indicators; assigning LOW severity
Routing
SOC
Unclassified report forwarded to SOC for manual review
Summary
A user reported receiving a phishing email impersonating Bybit
Severity factors
- Incident does not exhibit high-risk indicators; assigning LOW severity
Workflow
Recommended action
1. Review the report manually and reclassify into the appropriate incident type. 2. Gather additional information from the reporter. 3. Assess whether this is a real incident or a false positive. 4. Assign the correct response team based on further investigation.
Technical indicators (2)
by.bit.com
...d 'view your assets' it asked me to login and the link was 'by.bit.com' not 'bybit.com'
bybit.com
...ts' it asked me to login and the link was 'by.bit.com' not 'bybit.com'
Routing reasoning
SOC
- Unclassified report forwarded to SOC for manual review
- Analyst should review and reclassify as needed
Privacy findings (0)
No PII detected in this report.
Related incidents (0)
No related incidents found. Similarity is assessed at submission time.
Original report
[Analyst report] I got a message from Bybit on email saying I have been deposited with 10,000 USDT and I dont know who sent the email when I clicked the link that said 'view your assets' it asked me to login and the link was 'by.bit.com' not 'bybit.com'
Sanitized report
PII replaced with tokens for safe onward sharing.
[Analyst report] I got a message from Bybit on email saying I have been deposited with 10,000 USDT and I dont know who sent the email when I clicked the link that said 'view your assets' it asked me to login and the link was 'by.bit.com' not 'bybit.com'
Status history
NEW
21/09/2026, 14:34:21