I am sharing this incident in detail to raise awareness within the crypto community. What happened to me can happen to anyone, especially during live sessions and multitasking.
đ Location & Situation
At the time of the incident, I was present at Twin Tulips and hosting a live session on Binance Square. Alongside the live session, I was also involved in an important meeting on my mobile phone, which divided my attention.
đ Events Leading Up to the Hack
Two days before the incident:
â˘My Gmail account was compromised
â˘Using access to my email, the attacker attempted and later succeeded in accessing my Binance account â˘I immediately:
â˘Informed my Binance BDM
â˘Contacted Binance Customer Support â˘My Binance account already had 2FA enabled
đĽ Live Session & Co-Host Involvement
During the Binance Square live session:
â˘I noticed unusual behavior on my account
â˘I informed my co-host and clearly told them:
âPlease manage the live session, I need to focus on an urgent meeting on my mobile.â â˘While my co-host was handling the live session, I became fully engaged in the meeting on my phone
đ¨ Account Logout & Suspicious Activity
While I was distracted with the meeting: â˘My Binance account logged out automatically
â˘I was not actively monitoring the account due to the meeting and live session running simultaneously
When I returned:
â˘I attempted to log in again
â˘A QR code appeared on the screen with a message indicating that I had been logged out and needed to scan the QR code to re-login
đą QR Code Exploit
As soon as I: â˘Scanned the QR code
â˘My screen began to freeze and lag
â˘The account logged out again
â˘Immediately after, the account logged back in automatically
At that moment: â˘The attacker withdrew $831 from my Spot Wallet
đ¸ Financial Impact
â˘Total loss: $831
â˘Fortunately:
â˘No additional funds were available in the Spot Wallet
â˘Funds in the Earnings section remained untouched
â˘Either the attacker could not access those funds or failed to withdraw them
đ Reporting & Follow-Up
After identifying the unauthorized withdrawal:
â˘I contacted Binance Customer Support immediately
â˘Submitted a complete report, including:
â˘Timeline of events
â˘Screenshots
â˘Live session context
â˘The case was forwarded for internal investigation
â ď¸ Key Security Lessons
This incident highlights several critical lessons for all crypto users:
â Never underestimate email security
â Avoid scanning any QR code during high-pressure situations like live sessions
â Multitasking during live crypto events can increase risk
â Always assign a trusted co-host and stay alert during live sessions
â Immediately inform CS and BDM if any suspicious activity occurs
đ˘ Final Note to the Community
I am sharing this experience purely for community awareness.
In crypto, even a few minutes of distraction can lead to irreversible loss.
Please stay alert, secure your email first, and never ignore unusual behavior on your account.
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
My Binance Account Hack Community Awareness đ¨
Date of Incident: 09 January 2026
I am sharing this incident in detail to raise awareness within the crypto community. What happened to me can happen to anyone, especially during live sessions and multitasking.
đ Location & Situation
At the time of the incident, I was present at Twin Tulips and hosting a live session on Binance Square. Alongside the live session, I was also involved in an important meeting on my mobile phone, which divided my attention.
đ Events Leading Up to the Hack
Two days before the incident:
â˘My Gmail account was compromised
â˘Using access to my email, the
attacker attempted and later succeeded in accessing my Binance account
â˘I immediately:
â˘Informed my Binance BDM
â˘Contacted Binance Customer Support
â˘My Binance account already had 2FA enabled
đĽ Live Session & Co-Host Involvement
During the Binance Square live session:
â˘I noticed unusual behavior on my account
â˘I informed my co-host and clearly told them:
âPlease manage the live session, I need to focus on an urgent meeting on my mobile.â
â˘While my co-host was handling the live session, I became fully engaged in the meeting on my phone
đ¨ Account Logout & Suspicious Activity
While I was distracted with the meeting:
â˘My Binance account logged out automatically
â˘I was not actively monitoring the account due to the meeting and live session running simultaneously
When I returned:
â˘I attempted to log in again
â˘A QR code appeared on the screen with a message indicating that I had been logged out and needed to scan the QR code to re-login
đą QR Code Exploit
As soon as I:
â˘Scanned the QR code
â˘My screen began to freeze and lag
â˘The account logged out again
â˘Immediately after, the account logged back in automatically
At that moment:
â˘The attacker withdrew $831 from my Spot Wallet
đ¸ Financial Impact
â˘Total loss: $831
â˘Fortunately:
â˘No additional funds were available in the Spot Wallet
â˘Funds in the Earnings section remained untouched
â˘Either the attacker could not access those funds or failed to withdraw them
đ Reporting & Follow-Up
After identifying the unauthorized withdrawal:
â˘I contacted Binance Customer Support immediately
â˘Submitted a complete report, including:
â˘Timeline of events
â˘Screenshots
â˘Live session context
â˘The case was forwarded for internal investigation
â ď¸ Key Security Lessons
This incident highlights several critical lessons for all crypto users:
â Never underestimate email security
â Avoid scanning any QR code during high-pressure situations like live sessions
â Multitasking during live crypto events can increase risk
â Always assign a trusted co-host and stay alert during live sessions
â Immediately inform CS and BDM if any suspicious activity occurs
đ˘ Final Note to the Community
I am sharing this experience purely for community awareness.
In crypto, even a few minutes of distraction can lead to irreversible loss.
Please stay alert, secure your email first, and never ignore unusual behavior on your account.
For More Info:
@cz_binance @binance @BinancePk @heyibinance @BinanceResearch