DEV Community

Anoymask
Anoymask

Posted on Edited on

Bitget: $387.5M Stolen via Wallet Backend Compromise and Transaction Data Tampering

1. Basic Information

  • Article Name: Bitget Security Latest Incident Update: Fund Tracing and Recovery Bounty Program
  • Source: Bitget
  • Publication Date: 2026-09-25
  • Original: Bitget
  • Related Sources: BleepingComputer: withdrawal resumption, BleepingComputer: initial incident, Bitget: initial security notice, Bitget: phased withdrawal schedule, MITRE ATT&CK: Data Manipulation, BleepingComputer: security appliance zero-days, SlowMist investigation report, Mandiant status report
  • Related Malware, Threat Groups, CVEs, Products: North Korean threat actors (Bitget attribution), Bitget Exchange, third-party security appliances A and B, production wallet job server, hot wallet, warm wallet, wallet backend
  • Severity: Critical (Bitget confirmed that approximately $387.5 million was transferred from hot and warm wallets across multiple chains to attacker addresses due to the compromise of a critical backend system and the abuse of authorization processes.)

  • Revisions: Based on preliminary findings from Mandiant and SlowMist, incorporated zero-day compromises of two third-party security appliances, hidden scripts, web shells and C2, lateral movement to the wallet job server, malicious packages, and custom withdrawal tools.

  • Key Update (2026-10-01): Mandiant and SlowMist investigations revealed zero-day compromises of two third-party security appliances, web shells and C2, lateral movement to the wallet job server, malicious packages, and custom withdrawal tools.

2. In Brief

According to Bitget, attackers compromised a critical backend within the exchange's wallet infrastructure, manipulated transaction data, and abused authorization processes. Bitget confirmed the unauthorized transfer of approximately $387.5 million in cryptocurrency across multiple chains.

3. Attack Flow

Asset Theft via Authorization Abuse from Wallet Backend

  1. Attackers breached a critical backend system within Bitget's wallet infrastructure. The specific initial vector and vulnerabilities used remain unpublicized.
  2. According to statements by the Bitget CEO cited by BleepingComputer, the attackers abused the compromised backend to manipulate transaction data. Specific data fields modified and internal signing implementation details have not been disclosed.
  3. Based on the manipulated transaction data, legitimate authorization processes were triggered, advancing the transfer process. This does not mean it was confirmed that signing keys themselves were directly stolen or that data was intercepted and modified in transit.
  4. Assets were unauthorizedly transferred from hot and warm wallets spanning multiple blockchains (EVM-compatible chains, XRP Ledger, Zcash, and TRON) to addresses controlled by the attackers.
  5. Following the execution of transfers, the attackers distributed and moved funds across chains. Bitget and partner organizations are pursuing fund tracking and recovery, stating that some victim assets were frozen through coordination with industry stakeholders. While Mandiant and SlowMist participation in the investigation is public, individual freezing measures implemented by each company have not been detailed.
Processing System / Component Attacker Involvement and Impact Scope of Description Public Status and Unconfirmed Items
Wallet Backend Breached infrastructure and manipulated transaction data (CEO statement) Compromised backend and transaction data Specific initial entry vector and exploited vulnerabilities are unpublicized
Authorization Illegitimately triggered legitimate authorization processes using manipulated data Authorization processing upon receiving transaction data (details unpublicized) Bypassed verification conditions or specific bypass methods are unpublicized
Signing Potential abuse of legitimate signing workflows (inference) Signing architecture and verification processing unpublicized Direct theft of signing keys or in-transit modification unconfirmed in public info
On-Chain (Blockchain Transfers) Unauthorized transfer of approx. $387.5M across Ethereum/EVM, XRP, Zcash, and TRON Network transaction propagation and ledger recording Fund tracking ongoing; freezing of some victim assets announced. Individual measures by partners unpublicized

Invasion from Third-Party Security Appliances to Wallet Job Server (Additional Info as of 2026-10-01)

  1. The earliest malicious activity identified by SlowMist occurred on August 31, where a hidden script executed under Product A's service process, read environment variables containing database passwords, and connected to the database. Similar activity occurred on other nodes on September 23 and 25.
  2. Mandiant confirmed on September 24 that attackers gained privileged access to third-party security appliances A and B. Product names and zero-day details remain unpublicized.
  3. Attackers deployed a web shell on appliance B to establish C2, and moved laterally from persistent access to the production wallet job server.
  4. A malicious package was deployed to the job server, and a custom withdrawal tool was used to execute unauthorized transfers across multiple chains between 02:31 and 05:23 (UTC+8) on September 25.

4. Attacker Position and Execution Location

  • Attackers influenced transaction data from inside Bitget's wallet backend or from a position with privileges to operate that backend. Specific privileges and internal processes are unpublicized.
  • The primary public recipients of the transferred assets are attacker-controlled addresses across the EVM, XRP, Zcash, and TRON networks disclosed by Bitget.

5. Visibility for Victims and Administrators

Victims

  • User account balances are described by Bitget as protected and maintained, but a complete temporary suspension of withdrawals resulted in a period where assets could not be moved.

Administrators

  • Bitget detected unauthorized transfers from limited hot and warm wallets as anomalous. Specific details of internal authorization and signing logs, or at which stage alerts were triggered, have not been published.

6. Success and Failure Conditions

Success Conditions

  • Successfully breaching critical backend systems capable of generating or modifying wallet transactions.
  • Forcing authorization and transfer processes to accept manipulated transaction data. The presence of independent verification features or which checks were bypassed is unpublicized.
  • Presence of target assets in hot/warm wallets and the absence of manual or automated stop controls before transfer completion.

Failure Conditions and Risk Mitigation

Below are general defense and mitigation proposals in this report, and do not directly indicate internal configurations or implemented measures published by Bitget.

  • Strictly separate transaction generation systems from signing systems, re-verifying destinations, amounts, chain IDs, and nonces in an independent component immediately prior to signing.
  • Apply rate limiting, destination allowlists, multi-sig/quorum approval, and out-of-band confirmation to new destination addresses, high-value transfers, and simultaneous multi-chain transfers.
  • Minimize online hot wallet balances to operational necessities and establish an emergency kill switch mechanism to instantly block transfers across all chains upon anomaly detection.

7. What Happens Upon Success

  • Approximately $387.5 million in cryptocurrency was unauthorizedly transferred to attacker-controlled address groups.
  • Due to withdrawal suspensions, large-scale availability impacts occurred on user asset movement and exchange operations.
  • The extent to which the breached backend propagated to other credentials or wallet control privileges has not been published.

8. Observable Logs

Below are candidate infrastructure investigation items for your organization. References to HSMs and similar items target organizations deploying such equipment, and do not confirm their adoption or log acquisition status at Bitget.

  • Email: No evidence has been confirmed indicating email was used as a primary initial entry vector.
  • Proxy / SWG / DNS: Correlate management APIs, external SaaS, and unknown external destination traffic logs with known attacker infrastructure and normal management connection sources.
  • Endpoint / EDR: Scrutinize process trees, deployment history, access to secrets, modifications to binaries or configuration files, startup of management shells, and CI/CD execution history on wallet backend servers.
  • Identity / IdP: Check authentication and authorization logs for service accounts, signing approvers, HSM sessions, and administrator VPNs used within your organization. Bitget's HSM adoption status is unpublicized.
  • SaaS / Cloud: Reconcile parameters at transaction generation with signing digests, approval records, policy decisions, transmission payloads, and blockchain receipts using a unique transaction ID.
  • Network: Track outbound transfers to attacker addresses published in on-chain records, and separately check for traffic from the backend to unknown IP addresses and management ports. Differentiate between blockchain destination addresses and communication destination IPs.

9. Attack Success Determination

Confirmed in Public Information

  • Subsequent Breach Confirmed: Bitget officially described the backend compromise and the unauthorized transfer of approximately $387.5 million. Evidence such as specific unauthorized authentication records or malware execution traces remains unpublicized. (Target: Bitget exchange hot/warm wallets, multiple chains)

Criteria for Determination in Your Organization

  • Malware Execution or Successful Authentication Confirmed: Determination criteria: Unauthorized authentication success or malware execution is determined via authentication logs or process audit trails. General public descriptions of backend compromises alone do not substantiate specific attack execution methods. (Target: Internal backend investigation. Detailed authentication and execution records at Bitget are unpublicized)

10. Investigation Playbook

  • Investigation Origin: Initiate investigations upon the occurrence of unauthorized transfers, discrepancies between generated and signed transaction values, or alerts for high-value transfers to new destinations.
  • Initial Verification: Identify impacted wallets, chains, asset types, transaction hashes, approval personnel and systems, signing keys, and backend request sources.
  • Endpoint and Server Investigation: Execute forensic preservation of wallet backend systems, CI/CD environments, management jump hosts, and HSM integration components, investigating diffs and persistence traces.
  • Authentication and Cloud Investigation: Suspend the use of service accounts suspected of compromise, and revoke/replace related administrator credentials and API keys. If your organization uses an HSM, terminate affected sessions and replace HSM credentials as needed. Audit unauthorized privilege changes and verify the reflection of each measure.
  • Tracking Subsequent Operations: Track movement of funds from attacker addresses to cross-chain bridges, mixers, and other exchanges, and coordinate with relevant agencies to issue freezing requests.
  • Containment: Emergency-stop withdrawal functions, isolate the signing path from the network, and rebuild transaction verification capabilities in a clean environment.
  • Determination Categories: Clearly distinguish and record the stages of backend compromise, transaction data manipulation, signing execution, network broadcast, on-chain finalization, and fund freezing/recovery.

11. Defense and Detection Ideas

  • Single Events: Instantly detect and block transfers to addresses outside the whitelist, high-value transfers exceeding expected limits, transfers to unusual chains, and signed transactions inconsistent with policy.
  • Time-Series Correlation: Perform second-level correlation analysis of the sequence of events from backend access to transaction generation, approval, signing, broadcast, and on-chain transfer.
  • Threat Hunting: Retrospectively investigate past access logs for wallet backend secrets, deployment configurations, and management access paths.
  • Log Limitations: When neither pre-signing legitimate transaction data nor signed payloads are retained, post-incident identification of data manipulation points is difficult.
  • Priority Countermeasures: Prioritize deploying independent transaction verification infrastructure, physical and logical separation of key management from the backend, minimization of hot wallet balances, quorum approvals, and cross-chain kill switches.

12. Facts / Inference / Hypothesis

Facts

  • On September 24, 2026, Bitget detected multiple unauthorized transfers from limited hot and warm wallets and completely suspended withdrawals.
  • According to statements by the Bitget CEO cited by BleepingComputer, attackers compromised a critical backend of the wallet infrastructure, manipulated transaction data, and triggered authorization processes. Initial entry vectors and signing mechanism details remain unpublicized.
  • On-chain tracking as of September 25 confirmed by Bitget that approximately $387.5 million in cryptocurrency spanning Ethereum/EVM-compatible chains, XRP Ledger, Zcash, and TRON was transferred to attacker-controlled addresses.
  • Bitget explained that it identified and fixed the root vulnerability, contained the incident, and that no additional unauthorized transfers can occur. The official schedule planned for phased Bitcoin withdrawal resumption starting September 28 at 08:00 UTC, and BleepingComputer also reported the September 28 withdrawal resumption.
  • According to CEO statements cited by BleepingComputer, Bitget assesses that the behavior of attacker IPs and on-chain analysis results show high consistency with known patterns of North Korean threat actors. However, independent attribution confirmation by public authorities has not been shown.
  • Bitget stated that customer account balances are unaffected and losses will be fully covered by the exchange's Protection Fund. Mandiant and SlowMist are participating in the investigation.

  • Mandiant confirmed privileged access to third-party security appliances A and B, a web shell and C2 on appliance B, lateral movement to the production wallet job server, and malicious package deployment.

  • SlowMist confirmed activity starting August 31 where a hidden script under Product A's service process read environment variables containing database passwords and connected to the database.

  • Mandiant's preliminary report confirmed no evidence of private key compromise and stated that cold wallets remain unaffected.

Inference

  • If the backend is in a state where it can modify transaction contents intended for signing, assets can be unauthorizedly transferred by abusing legitimate signing workflows without directly stealing the wallet's cryptographic keys themselves.
  • Withdrawal resumption indicates progress in containment and safety verification, but does not independently prove the complete elucidation of entry vectors or the total resolution of potential subsequent risks.

Hypothesis

No additional hypotheses. Unconfirmed items are documented in "14. Unknowns and Additional Investigation".

13. MITRE ATT&CK Mapping

ID Technique Confidence Basis
T1565 Data Manipulation medium Corresponds to the manipulation of transaction data stated in the CEO explanation. Because it is unpublicized whether the modification was implemented in stored data, transit paths, or runtime processes, it remains at the parent technique level.
T1657 Financial Theft high Unauthorizedly transferred cryptocurrency to attacker-controlled address groups.

14. Unknowns and Additional Investigation

  • Initial entry vector into critical backend systems and specific exploited vulnerabilities.
  • The boundary (signing policy, approval flow, HSM, or related components) where transaction data manipulation was established.
  • Objective evidence for attribution to North Korean threat actors, as well as the attacker's initial entry date/time and dwell time.
  • Product names, zero-day identifiers, patched versions, and exploit primitives for third-party security appliances A and B.
  • IOCs for hidden scripts, web shells, malicious packages, and custom withdrawal tools.
  • Credentials and protocols used when moving from appliance A to B, and B to the wallet job server.

15. Impact on SOCs and Organizations

For cryptocurrency exchanges and organizations providing custody services, securing hot wallet private keys is insufficient; ensuring the integrity of the backend generating transactions prior to signing, as well as independent verification of destinations, amounts, and chain IDs, is essential. For high-value transfers, new addresses, and simultaneous multi-chain transfers, a multi-layered defense is required that does not blindly trust parameters passed from the backend, mandating separated policy verification engines and out-of-band approvals.

This update demonstrates the necessity of monitoring security appliances not as entities outside the trust boundary, but as privileged execution nodes. Financial and cryptocurrency businesses in Japan must detect environment variable reading by appliance processes, database connections, web shells, C2, and east-west traffic to production job servers with high priority, independently verifying wallet authorization and job execution.

16. Summary by Target Audience

  • For SOCs: Time-series correlate backend access to signing, broadcasting, and on-chain transfers, tracking outbound transfers to published attacker addresses and subsequent fund movements.
  • For Administrators: Establish independent verification systems for transaction-to-be-signed data, reduce hot wallet holdings, tighten approval quorums, and ready cross-chain immediate-stop kill switches.
  • For Users: According to Bitget, there are no direct losses to customer account balances. Verify officially guided phased withdrawal resumption schedules and the latest security notices.

Top comments (0)