CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

Bitget hot/warm-wallet theft (September 2026)

incident · incident:bitget-hot-wallet-theft-2026-09

Theft of approximately $388M from cryptocurrency exchange Bitget's hot and warm wallet infrastructure on 2026-09-24. Mandiant's status report: privileged access to two third-party security appliances, a web shell and command-and-control on one, then lateral movement to the production wallet job server. SlowMist dates the earliest malicious activity to 2026-08-31 through a zero-day in a service on one appliance node (Mandiant, 2026-09-28, SlowMist, 2026-09-29). Bitget's CEO calls North Korean involvement very likely. TRM Labs finds the laundering wallets overlap those of the Bybit and AFX Bridge thefts, which it calls previously identified North Korean thefts, and says the laundering group is the same one TraderTraitor used in other recent hacks, while stating it has not definitively attributed the exploit (TRM Labs, 2026-09-25). No relation edge is recorded pending attribution.

Coverage
1
first 2026-09-29 → last 2026-10-11
Latest activity
2026-09-30
Compromised security appliances, not a key theft, gave the attacker a path to Bitget's wallet server
Peak priority
notable
1 notable
Targets
finance
sectors: finance
Sources cited
7
5 hosts

Defender insights

What each entry about Bitget hot/warm-wallet theft (September 2026) tells a defender to do, newest first.

2026-09-29NOTABLECompromised security appliances, not a key theft, gave the attacker a path to Bitget's wallet server

Detection

Story timeline

  1. 2026-09-29Bitget: an attacker compromised two third-party security appliances, moved laterally to the wallet job server and stole $388M in one of 2026's largest crypto-exchange hacks
    active-threatsCompromised security appliances, not a key theft, gave the attacker a path to Bitget's wallet server
ATT&CK techniques (9 across 8 tactics)

9 techniques observed across 1 entry about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v20.1 · compare on the matrix · Navigator layer (JSON)

  • Initial AccessValid Accounts
  • ExecutionCommand and Scripting Interpreter
  • PersistenceValid Accounts · Server Software Component: Web Shell
  • Privilege EscalationValid Accounts
  • StealthIndicator Removal: File Deletion · Valid Accounts
  • Credential AccessUnsecured Credentials
  • Lateral MovementLateral Tool Transfer
  • ImpactData Manipulation: Stored Data Manipulation · Data Manipulation: Transmitted Data Manipulation · Financial Theft

Initial Access TA0001

T1078Valid Accounts×1

Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.

Evidence: 2026-09-29/bitget-hot-wallet-theft-north-korea-nexus · ATT&CK page ↗

Execution TA0002

T1059Command and Scripting Interpreter×1

Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries. These interfaces and languages provide ways of interacting with computer systems and are a common feature across many different platforms. Most systems come with some built-in command-line interface and scripting capabilities, for example, macOS and Linux distributions include some flavor of Unix Shell while Windows installations include the Windows Command Shell and PowerShell.

Evidence: 2026-09-29/bitget-hot-wallet-theft-north-korea-nexus · ATT&CK page ↗

Persistence TA0003

T1078Valid Accounts×1

Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.

Evidence: 2026-09-29/bitget-hot-wallet-theft-north-korea-nexus · ATT&CK page ↗

T1505.003Server Software Component: Web Shell×1

Adversaries may backdoor web servers with web shells to establish persistent access to systems. A Web shell is a Web script that is placed on an openly accessible Web server to allow an adversary to access the Web server as a gateway into a network. A Web shell may provide a set of functions to execute or a command-line interface on the system that hosts the Web server.

Evidence: 2026-09-29/bitget-hot-wallet-theft-north-korea-nexus · ATT&CK page ↗

Privilege Escalation TA0004

T1078Valid Accounts×1

Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.

Evidence: 2026-09-29/bitget-hot-wallet-theft-north-korea-nexus · ATT&CK page ↗

Stealth TA0005

T1070.004Indicator Removal: File Deletion×1

Adversaries may delete files left behind by the actions of their intrusion activity. Malware, tools, or other non-native files dropped or created on a system by an adversary (ex: Ingress Tool Transfer) may leave traces to indicate to what was done within a network and how. Removal of these files can occur during an intrusion, or as part of a post-intrusion process to minimize the adversary's footprint.

Evidence: 2026-09-29/bitget-hot-wallet-theft-north-korea-nexus · ATT&CK page ↗

T1078Valid Accounts×1

Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.

Evidence: 2026-09-29/bitget-hot-wallet-theft-north-korea-nexus · ATT&CK page ↗

Credential Access TA0006

T1552Unsecured Credentials×1

Adversaries may search compromised systems to find and obtain insecurely stored credentials. These credentials can be stored and/or misplaced in many locations on a system, including plaintext files (e.g. Shell History), operating system or application-specific repositories (e.g. Credentials in Registry), or other specialized files/artifacts (e.g. Private Keys).

Evidence: 2026-09-29/bitget-hot-wallet-theft-north-korea-nexus · ATT&CK page ↗

Lateral Movement TA0008

T1570Lateral Tool Transfer×1

Adversaries may transfer tools or other files between systems in a compromised environment. Once brought into the victim environment (i.e., Ingress Tool Transfer) files may then be copied from one system to another to stage adversary tools or other files over the course of an operation.

Evidence: 2026-09-29/bitget-hot-wallet-theft-north-korea-nexus · ATT&CK page ↗

Impact TA0040

T1565.001Data Manipulation: Stored Data Manipulation×1

Adversaries may insert, delete, or manipulate data at rest in order to influence external outcomes or hide activity, thus threatening the integrity of the data. By manipulating stored data, adversaries may attempt to affect a business process, organizational understanding, and decision making.

Evidence: 2026-09-29/bitget-hot-wallet-theft-north-korea-nexus · ATT&CK page ↗

T1565.002Data Manipulation: Transmitted Data Manipulation×1

Adversaries may alter data en route to storage or other systems in order to manipulate external outcomes or hide activity, thus threatening the integrity of the data. By manipulating transmitted data, adversaries may attempt to affect a business process, organizational understanding, and decision making.

Evidence: 2026-09-29/bitget-hot-wallet-theft-north-korea-nexus · ATT&CK page ↗

T1657Financial Theft×1

Adversaries may steal monetary resources from targets through extortion, social engineering, technical theft, or other methods aimed at their own financial gain at the expense of the availability of these resources for victims. Financial theft is the ultimate objective of several popular campaign types including extortion by ransomware, business email compromise (BEC) and fraud, "pig butchering," bank hacking, and exploiting cryptocurrency networks.

Evidence: 2026-09-29/bitget-hot-wallet-theft-north-korea-nexus · ATT&CK page ↗

Entries about Bitget hot/warm-wallet theft (September 2026) (1)

2026-09-29 · view entry permalink →

NOTABLEupdatedNATOB2

Bitget: an attacker compromised two third-party security appliances, moved laterally to the wallet job server and stole $388M in one of 2026's largest crypto-exchange hacks

Cryptocurrency exchange Bitget confirms that, at 18:31 UTC on 2026-09-24, unauthorized transfers occurred from a portion of its hot and warm wallet infrastructure across eleven blockchains: Ethereum, XRP Ledger, TRON, Arbitrum, Optimism, Base, BNB Smart Chain, Avalanche, Algorand, Celestia and Zcash (Bitget, 2026-09-27). Per Bitget's own investigation, the attacker did not steal a private key: the attacker "exploited a vulnerability in a third-party security product to obtain high-level internal credentials" and used them "to send fraudulent withdrawal commands to the wallet system", bypassing existing risk controls (Bitget, 2026-09-27). CEO Gracy Chen described the mechanism directly: "The attacker compromised a critical backend system within our wallet infrastructure, used it to spoof transaction data, and triggered our authorization process to move funds out" (The Hacker News, 2026-09-25). Bitget states private-key compromise was ruled out, cold wallets were unaffected and the underlying vulnerability was remediated; the third-party vendor was notified and the affected functionality disabled (Bitget, 2026-09-27).

Total loss is now estimated at approximately $388M across twelve wallet addresses (Bitget, 2026-09-27), up from the USD 351.6M loss Bitget first reported, the figure TRM Labs uses in its analysis (TRM Labs, 2026-09-25). Bitget says its Protection Fund covers the financial impact (Bitget, 2026-09-27), a fund Bitget sizes at USD 464 million, according to TRM Labs (TRM Labs, 2026-09-25). Customer account balances, deposits and trading were unaffected, and withdrawals, paused at detection, resumed in phases starting with Bitcoin on 2026-09-28. Bitget revoked and reissued internal login credentials, restructured access to highly sensitive systems, now requires multiple approvals for critical operations, and engaged Mandiant and SlowMist for independent forensics (Bitget, 2026-09-27).

Bitget's CEO called North Korean involvement "very likely," based on the team's preliminary investigation linking observed IP addresses to VPN services associated with a North Korean hacking group (TRM Labs, 2026-09-25). TRM Labs, an independent blockchain-forensics firm, reports multiple on-chain overlaps with wallets used to launder earlier North Korean thefts, including Bybit and AFX Bridge, through a laundering network it has not linked to any other group's thefts, so the overlaps point to TraderTraitor: "these onchain links confirm the group laundering these proceeds is the same one used by TraderTraitor in other recent hacks" (TRM Labs, 2026-09-25). TRM is explicit that this stops short of definitive attribution: "TRM has not yet definitively attributed the exploit to North Korea" and "another actor carrying out the theft remains technically possible."

The latest investigation found that the attacker exploited a vulnerability in a third-party security product to obtain high-level internal credentials.

Bitget (official incident page) 2026-09-27

The attacker compromised a critical backend system within our wallet infrastructure, used it to spoof transaction data, and triggered our authorization process to move funds out.

Bitget CEO Gracy Chen, via The Hacker News

these onchain links confirm the group laundering these proceeds is the same one used by TraderTraitor in other recent hacks

TRM Labs 2026-09-25

The threat actor deployed a web shell onto the security appliance B and established a Command-and-Control (C2) connection.

Mandiant (Google Cloud)

The earliest malicious activity identified in the available logs dates to August 31.

SlowMist 2026-09-29
Updaterun 2026-09-30T0639Z-auditpriorityupdated_attitleheadlinesummarytechniquessourcesevidencesourcing_notebody

Bitget released the independent investigation reports from Mandiant and SlowMist on 2026-09-30. Both identify the compromise of third-party security products as what enabled access to the wallet environment (Bitget, 2026-09-30). Mandiant's status report states that on 2026-09-24 the attacker "gained unauthorised privileged access to Bitget's third party security appliances A and B", deployed a web shell on appliance B, established a command-and-control connection, and used that persistent access to move laterally to Bitget's production wallet job server and deploy malicious packages (Mandiant, 2026-09-28).

The two reports date different events and label the appliances independently: Mandiant dates the attacker's privileged access to appliances A and B to 2026-09-24 (Mandiant, 2026-09-28), while SlowMist dates the earliest malicious activity in its logs, on a node of its Product A, to 2026-08-31 (SlowMist, 2026-09-29).

SlowMist dates the earliest malicious activity in the available logs to 2026-08-31: a zero-day vulnerability in a service on one of Product A's nodes let the attacker run a hidden script under the service process, read the environment variable holding the database password and connect to the database, and the same hidden-script activity appeared on two more nodes on 2026-09-23 and 2026-09-25 (UTC+8). Early on 2026-09-25 (UTC+8) the attacker entered Product B's management platform under an internal employee's identity, made three attempts to inject system commands into task parameters to write malicious files, and then submitted code through the platform's web execution endpoint, attempting to modify server configuration, write a communication relay file and upload and assemble malicious program files in batches. SlowMist also recovered, from files the attacker had deleted, a withdrawal tool built for Bitget's withdrawal logic that forged risk-control parameters and invoked the withdrawal process, and records that the attacker later tried to alter withdrawal records directly in the wallet database (SlowMist, 2026-09-29). Neither report names the appliance vendors.

For defenders, the appliance class is security and network appliances with privileged reach into a production backend, and the observable behaviour is a web shell or hidden script running under the appliance's own service process, a new outbound command-and-control connection from the appliance, and sessions from the appliance to production servers (Mandiant, 2026-09-28) (SlowMist, 2026-09-29).

Correctionrun 2026-10-11T1307Z-auditbodyevidence

Bitget says "The affected systems were isolated and the underlying vulnerability was remediated. The relevant third-party vendor was notified and the affected functionality was disabled" (Bitget, 2026-09-27). It does not say the functionality stays disabled until the vendor ships a fix. Bitget's incident page, since updated, now states without a hedge that the attacker exploited a vulnerability in a third-party security product to obtain high-level internal credentials, and that private-key compromise has been ruled out (Bitget, 2026-09-27).

Builds on: SentinelLabs: the same DPRK backdoors from a $292M crypto theft resurface on a victim with no…

incident29 Sep 05:15Zmulti-sourceOpen finding →

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Where this entity is cited

  • Threats1

Source distribution

  • bitget.com2 (29%)
  • thehackernews.com2 (29%)
  • img.bgstatic.com1 (14%)
  • raw.githubusercontent.com1 (14%)
  • trmlabs.com1 (14%)