Bybit

Case No. #19139103 Incident Summary Unauthorized withdrawal of 415.9514 USDT via BSC (BEP20) occurred at 02:18:17 on July 3, 2025. A new withdrawal address was added to my account automatically: 0x262fade26c89c3d1eb59adf57ddd2d597255dbeb This action was performed without 2FA verification and without any confirmation email, violating the basic principles of withdrawal whitelisting. The IP used for this action (181.115.208.245) is completely foreign to my normal login activity. I had Google Authenticator enabled and active at the time of the incident. There is no record of phishing attempts, leaked credentials, or malware infection from my side. My devices were scanned, reset, and secured following your instructions. ❌ Issues With Bybit's Response No explanation was provided as to why 2FA and email confirmation were bypassed when adding a withdrawal address. The response blames the user’s device security without any transparent or technical investigation from Bybit’s backend. No audit trail or investigation report has been shared regarding the login or withdrawal process. The case was closed prematurely, avoiding accountability or follow-up on a potentially systemic vulnerability. 📢 My Position This incident highlights a serious security gap in the protection layers of Bybit’s withdrawal mechanism. I followed all protocols, had all security features enabled, and the breach still occurred. The fact that: A whitelisted withdrawal address was added automatically, No verification was requested, and Funds were withdrawn without my action, proves that the incident was not caused by my device, but by a failure within Bybit’s own systems or security flows. Your advice to contact “local authorities” completely ignores this fact, placing all liability on the user without offering transparency or technical accountability from the platform.