Digital Asset
Intelligence
Theme

Search 3CBlock

News, exchanges, regulatory intelligence, reviews and Voices.

Security Incident · Tron Ecosystem

Bitget Internal System Compromise: $387.5M Reported Loss

Historical incident record

Incident Overview

At 18:31 UTC on September 24, 2026, Bitget detected unauthorized transfers from parts of its hot and warm wallet infrastructure. Attackers compromised a critical backend system in the wallet stack, spoofed transaction data, and triggered Bitget’s own authorization process to move funds out. The firm ruled out private-key theft and fake user withdrawal requests. The loss was first put at about $351,600,000 and later revised to about $387,500,000 after Zcash and TRON assets were included. Cold wallets and Bitget Wallet were unaffected. Withdrawals were paused, the User Protection Fund is said to cover the loss, and some attacker addresses have been frozen.

Sources & References

This record presents information attributed to the linked sources. Incident dates describe the original event, not a new report. Reported loss figures reflect the source record and are not current market valuations.

More Security Incidents

View All →
  1. Incident date
    Target

    Chainflip

    Attack methodProtocol logic vulnerability
    Reported loss$ 736,442.17
  2. Incident date
    Target

    TRON DAO

    Attack methodAccount Compromise
    Reported lossNot disclosed
  3. Incident date
    Target

    HTX

    Attack methodDDoS Attack
    Reported lossNot disclosed
  4. Incident date
    Target

    TRON

    Attack methodMultisig Vulnerability
    Reported lossNot disclosed
  5. Incident date
    Target

    SharkTron

    Attack methodRug Pull
    Reported loss$ 10,000,000
  6. Incident date
    Target

    Fake GIWA Bridge

    Attack methodFake Chain / Fake Bridge Scam
    Reported loss$ 2,000,000
  7. Incident date
    Target

    Duelbits

    Attack methodPrivate Key Leakage
    Reported loss$ 7,000,000