Hatim 🔸 حاتم

CZ follows me and this is not an April fool

An update on the security incident.

تحديث التحقيق: أشارت نتائج تحقيقنا الأولية إلى أن الحادث الأمني قد يكون قد شمل جهاز كمبيوتر محمولًا مخترقًا، إلا أن تحقيقاتنا اللاحقة كشفت عن نقاط اختراق إضافية. كان هذا هجومًا معقدًا، ونحن نبذل كل ما في وسعنا بالتنسيق مع جهات إنفاذ القانون لمعالجة الأمر. وما زلنا نجمع الحقائق، وسنشارك المزيد من المعلومات بشكل مباشر فور توفرها. ستغطي Binance جميع الخسائر من صندوق SAFU ومن أموال الشركة. أموال المستخدمين آمنة. ولا نزال ملتزمين بالجدول الزمني المتوقع لاستئناف خدمة السحب خلال 45 ساعة. وتظل عمليات الإيداع غير متأثرة. وقد توقفت التدفقات الخارجة عندما قمنا بإيقاف خدمة السحب في وقت سابق. وما زلنا نعمل مع الشركاء لتجميد العديد من الأصول المتأثرة، وقد قمنا حتى الآن بتجميد ما يقارب 3 مليارات دولار. سنواصل تقديم المزيد من التحديثات عبر قنوات بينانس الرسمية فور توفر معلومات مؤكدة إضافية.

Investigation update: Our initial investigation suggested that the security incident may have involved a compromised laptop, however our subsequent investigation has uncovered additional points of breach. This was a complex attack, and we are doing all we can in coordination with law enforcement to resolve it. We are still gathering the facts, and will share more directly as we have them. Binance will cover all losses from the SAFU fund and the company’s funds. User funds are safe. We are still on track towards the expected timeline to resume the withdrawal service in 45 hours. Deposits remain unaffected. The outflows ceased when we paused withdrawal service earlier. We are still working with partners to freeze many of the impacted assets, and have frozen around $3 billion thus far. We will continue to provide further updates through official Binance channels as more verified information becomes available.

I want to speak to you directly about what happened. Bottom line - your money is safe, and we're covering every loss. Our initial investigation suggests this security incident may have started with a compromised DevOps engineer's laptop. That gave an attacker access to a service container, where they submitted unauthorized withdrawal transactions. To be clear: the attacker did not simply use one engineer's permissions, and this was not a single "one-click" action. It involved a more complex attack process. Our investigation has not attributed responsibility to any individual. So far, we have found no evidence of any wallet private key leak. We'll share a detailed technical post-mortem once the investigation is complete and every fact is verified - and publish an updated Proof of Reserves once remediation is complete. What you need to know: • Your funds are safe • Binance will cover all losses from the SAFU fund and company funds • Estimated total impact: ~$6.3B, with ~$3B frozen on-chain so far, in coordination with our blockchain partners • No evidence of any wallet private key leak • Deposits are unaffected and operating as normal What we've done: • Temporarily suspended withdrawals while we complete a security revamp of the withdrawal service and its related addresses • Revoked the affected address authorizations • Engaged law enforcement and blockchain intelligence partners to trace and recover funds Our team hasn't stopped. We're working closely with law enforcement to ensure the matter is handled appropriately - and I'll share what I can, as soon as I can.

Nos équipes sont au courant de rapports faisant état d'un éventuel problème de sécurité et enquêtent activement. Les fonds des utilisateurs sont totalement en sécurité. Nos équipes de sécurité examinent toutes les informations pertinentes en urgence, et nous publierons des mises à jour via les canaux officiels de Binance dès que nous disposerons d'informations vérifiées. Nous vous prions de rester prudents face aux arnaques et de ne pas faire confiance aux liens, messages ou demandes d'informations de compte non officiels.

Service Update Deposits remain unaffected and continue to operate as normal. Withdrawals remain paused while our team completes a security revamp of the withdrawal service and its related addresses. We expect to resume within 48 hours, and will update with further details. The incident stems from multiple factors. Our security team is tracing the full attack path through the compromised computer which may be the entry point of the incident. A comprehensive report with the root cause will follow. We will continue to share updates through official Binance channels.

Double the leadership. Double the takes. Yi He and Richard Teng join #BinanceBlockchainWeek in Bangkok for a conversation on where Binance — and the industry — goes next. 🗓 28–29 Nov 2026 Be there for the takes → binanceblockchainweek.com

Join our Discord AMA! 📅 Friday, Oct 30, 13:00 UTC 💰 15 selected questions earn 10 USDC each 🏆 Kahoot: Top 10 share 100 USDC Drop your questions in #builders-chat with #ai discord.com/channels/8825544… Come learn, play & win! 💛

This Halloween, the scariest thing isn't the ghosts - it's the scams👻 #SAFUHalloween is a 6-day community challenge where users inspect a Halloween-themed Binance visual and identify 5 hidden crypto scams/red flags. To add a crypto-native element, users will also predict the BNB price at 23:59 UTC on October 31. How to Participate👇 1- Identify all 5 crypto scams/red flags hidden in the image. 2- Predict the BNB price at 23:59 UTC on October 31. 3- Comment your 5 answers + BNB price prediction. 4- Follow @HatimBinance and @HaMyBinance on X. 5- Include #SAFUHalloween in your entry. 6- Repost this post

🧠 Tomorrow: Binance AI, AI Pro and Agent OS, Explained 👀One app. Three AI products. And one big question: which one is right for you? Tomorrow we break it all down in simple words, so you can choose with confidence. What we’ll cover: ✅ Binance AI ✅ Binance AI Pro ✅ Agent OS ✅ What’s the difference between all of them 📍 When: Tomorrow, October 27, Tuesday at 1 PM UTC 📍 Where: binance.com/en/square/audio?… Set your reminder now, so you don’t miss it. See you there! 🚀 ⚠️ Not financial advice. Features may not be available in all regions.