Independent record. Not associated with, endorsed by or operated by Binance. This site is read-only: there is nothing to sign in to, pay for or connect.
An independent record of the October 2026 Binance hack
Newest first. The raw hash is the SHA-256 of the stored copy exactly as fetched. We keep the copy privately and publish its hash. The text hash is of the text extracted from it, which is what is compared between captures.
| Captured (UTC) | Fetched via | HTTP | Raw sha256 | Text sha256 | Text changed |
|---|---|---|---|---|---|
| http | 200 | a9be05a5ddbec31ec6abcbf5e2d77bdaae84124fae5c48787d7d7e88a3b9283b | b1d0789bdd1ee7bf8fb545524817e51b2f8b2e98b7cdccca991060faaeecd80c | No |
No text changes detected between captures of this source.
You split it into thousands and then use hardware security modules with a risk management system so it doesn't let you transfer $5bn instantly. Unless it was an inside job maybe? I'd be really curious to know what their security architecture was.