North Korea ‘Very Likely’ Behind $388 Million Hack of Crypto Exchange Bitget
Crypto exchange Bitget says North Korea is very likely behind a theft of about $387.5 million that did not require anyone to steal the keys to the vault. Security systems at the Seychelles-based platform flagged unauthorized transfers from some of its hot wallets at 18:31 UTC on Thursday, according to an official incident notice and a post from CEO Gracy Chen. The breach reached parts of Bitget’s hot and warm wallet layers.
- ▪Crypto exchange Bitget says North Korea is very likely behind a theft of about $387.5 million that did not require anyone to steal the keys to the vault.
- ▪Security systems at the Seychelles-based platform flagged unauthorized transfers from some of its hot wallets at 18:31 UTC on Thursday, according to an official incident notice and a post from CEO Gracy Chen.
- ▪The breach reached parts of Bitget’s hot and warm wallet layers.
Gizmodo files mainly under tech. We currently carry 1,347 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Gizmodo |
| Canonical URL | https://gizmodo.com/north-korea-very-likely-behind-388-million-hack-of-crypto-exchange-bitget-2000817421 |
| Publication time | Fri, 25 Sep 2026 15:50:32 +0000 |
| Retrieval time | 2026-09-25T15:55:32.299Z |
| Last seen | 2026-09-25T15:55:32.299Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 5yZHosZ0Phr1 · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Crypto exchange Bitget says North Korea is very likely behind a theft of about $387.5 million that did not require anyone to steal the keys to the vault. Security systems at the Seychelles-based platform flagged unauthorized transfers from some of its hot wallets at 18:31 UTC on Thursday, according to an official incident notice and a post from CEO Gracy Chen. The breach reached parts of Bitget’s hot and warm wallet layers. Cold wallets, which sit offline, were not hit. To be clear, the hack only affected Bitget Exchange. Bitget Wallet users were not affected. [SECURITY NOTICE] Bitget Hot Wallet Incident — September 24, 2026 At 18:31 UTC on September 24, 2026, Bitget's security systems detected unauthorized transfers from some of our hot wallets.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Gizmodo.
Discussion
0 commentsMore from Gizmodo
