bitgetceoconfirms

#BitgetCEOConfirms $388MStolenInHack

Bitget CEO Gracy Chen confirmed that approximately $387.5 million in crypto assets were transferred to attacker-controlled addresses during the September 24 security incident. The figure increased from the initial $351.6 million estimate after additional Zcash and TRON transfers were identified.

According to Bitget, the attackers did not obtain private keys. Instead, they compromised a backend wallet system, spoofed transaction information, and triggered the platform’s authorization process. Bitget says the vulnerability has since been identified and remediated.

Bitget also says its User Protection Fund exceeds $464 million and that user balances remain unaffected. Withdrawals are being restored in phases while additional security checks continue.

Discussion:
“Bitget’s confirmed $387.5M loss highlights how critical backend security and transaction verification are for centralized exchanges. The key focus now is fund recovery, transparent incident reporting, and safely restoring withdrawals while protecting user assets.”

Bitget update withdrawal status restored｜No VIP-only early channel｜BNB near $762, I’ll wait for now

My stance: I’ll check the recovery progress, but I won’t pay for prioritized withdrawals or chase BNB rebounds. On the forum this round, the CEO confirmed the loss topic had 14 views and 4 discussions—same as the previous round; BNB is not on the six-hour search list. The exchange event is not a new failure on the BNB Chain, and it’s also not evidence of new BNB buy demand.

There’s an update this time: Bitget’s English official statement says BTC withdrawals begin resuming on September 28 at 08:00 UTC. The Bitcoin and BSC channels are open. Their public interface at the same time marks BTC and the BEP20 network as withdrawable, so you can cross-check; I haven’t tested whether funds arrive instantly for every transaction, so I can’t guarantee completion time. The BSC channel being open doesn’t mean BNB itself is already withdrawable.

More importantly, the key safety boundary in the updated statement is clear: regular users, institutions, VIPs, and employees all follow the same public queue schedule—there are no separate withdrawal channels or priority eligibility. The official announcement dated September 26 also states that all user categories are subject to the same staged schedule without any special extra action required by users before recovery. The two official documents corroborate each other rather than relying on a one-line promise from customer support in private chats. Other tokens remain in later queues; the specific coins and network status must be checked within the platform.

Why does this affect the crypto market? This is my independent judgment: the anxiety between suspension and restoration may make people willing to give up safety checks for a “green lane.” If anyone asks you to transfer BNB to a private address first, share your recovery phrase, or sign an unclear authorization, you shouldn’t use a CEO livestream or a public foundation statement to validate that request. This is to prevent possible impersonation scams—not to claim that new victim cases have already been discovered in this round. The official Chinese safety warning also emphasizes not sharing private keys, passwords, or verification codes, and it reminds people to be wary of non-official recovery services.

I’ll verify the dates, assets, and networks by opening the official entry myself, without jumping from unfamiliar links. “Withdrawals are available” doesn’t mean the investigation of everything is finished, and it doesn’t mean your funds are already bought into BNB. Refusing to buy nonexistent priority eligibility is the focus of this time.

Actual market status: Kraken’s BNB/USD rechecked before publication at $762.37. Over the past 24 hours it ranged from $757.85 to $784.04, and it hasn’t returned to my $766 confirmation level. The price has rebounded somewhat from the window low, but there’s no event-window evidence to attribute the move to withdrawal restoration; $757.85 is also not a guaranteed support.

If I were trading for myself: I wouldn’t participate right now; position is 0%. I’d only consider unleveraged spot longs and not short. If the hourly close is above $766, then a pullback to $764–$766 holds, and the platform’s quotes and deposits/withdrawals are normal, I would use up to 0.3% of total funds to participate. Half at $772, close the remainder at $778. Hard stop at $761, or fully exit if two consecutive hourly closes are below $764. If it breaks below $756 before entry, the plan is canceled. Only once it’s standing above $766 would I overturn the “not participating yet” judgment. Even if the channel breaks upward due to anomalies, I won’t enter, and I won’t average down. This is the plan—not a completed trade or realized profit.

Source: [Bitget update announcement](https://www.bitget.com/amp/academy/bitget-security-incident-what-happened-timeline-impact-response), the September 26 restoration announcement and the Chinese safety reminder; Kraken market data.
#BitgetCEOConfirms$388MStolenInHack #BTC #BNB
The above is only my personal market observation and does not constitute investment advice.

Bitget security discussion increases｜Separate the first transfer from discovering anomalies｜XMR around $530; I’ll wait first

My view is: first check the event timestamps, don’t treat “discovering anomalies” as “the attack just began,” and don’t chase privacy coins just because of security news. The Bitget Square accurate topic this round, #BitgetCEOConfirms$388MStolenInHack, shows 11 people discussing; the previous round had 4. Increased attention can be confirmed, but the number of people discussing is not a measure of fund flows, and it’s not evidence that the incident has reached final forensic conclusions.

The first-hand basis is Bitget’s updated official incident statement. The timeline states: at 18:31 UTC on September 24, the first unauthorized transfer occurred; at 19:05, the reconciliation system detected a major discrepancy and automatically blocked the platform’s withdrawal requests; at 19:14, the highest-level emergency response was initiated; and at 19:40, containment measures began. The disclosure times of the first two points are about 34 minutes apart. This is the interval I calculated from the official timestamps; it does not prove the attack lasted a full 34 minutes, and it can’t be used to estimate loss per minute. The date belongs to the original event, not another attack happening again today.

I also cross-checked the official update on September 25: the investigation and tracking are still ongoing, and any additional loss figures are based on transaction categorization from the original incident; it does not mean new transfers were added after control was established. Both documents are platform disclosures; they can’t be used to pretend I have obtained independent, complete audits. For the attack path, third-party products, and the attacker’s identity, we should continue to distinguish preliminary judgments from final conclusions. For attributions that haven’t been verified, I won’t draw conclusions.

How does this affect crypto trading? My judgment is that abnormal activity, system identification, restricting actions, and full isolation are different stages. The screen still shows the balance; that alone is not enough to claim that a particular moment’s fund channel was safe and usable. Post-incident alerts also don’t equal a stop before the fact. Traders need to assess where the funds are sitting, operation permissions, and the exit path; they can’t just look at the single sentence “emergency response has been initiated” and immediately restore their original risk budget.

For XMR, this is an observation of cross-market custody and trust risk—not evidence that the Monero protocol has been broken. Privacy features can’t complete reconciliation for a third-party platform, and they also don’t guarantee that the coin price is immune to liquidity contraction. I haven’t verified evidence in this round’s incident that involves XMR, and I also have no evidence proving that funds are currently moving from the impacted assets into XMR. Therefore, I’m not writing “privacy as a hedge” as a rotation that has already happened.

How has the market reacted? I rechecked Kraken’s XMR/USD quote: about $530.28. The rolling 24-hour low is $525.59 and the high is $556.00; it’s still on the lower side of the range. A price snapshot can’t prove the event caused the pullback. $536 is my rebound confirmation line; $524 is the line to cancel before entry—neither guarantees valid support/resistance. If later official reports change the risk assessment, or if the trading channels used show abnormal status, I will withdraw from the plan.

If I were trading it myself, I wouldn’t participate now; my position is zero, and I won’t short or add leverage. Only if the 1-hour chart closes above $536, then pulls back to hold between $534 and $536, and the quote and the channels used are normal, would I consider using up to 0.3% of total capital for a spot long trial; cut in half at $542 and close the remaining position at $548. If, after entry, it hits a hard stop-loss at $531, or if two consecutive hourly candles close below $534, I’ll close all remaining positions. If it breaks below $524 before entry, I cancel the plan and don’t average down losses. Arrangements that haven’t been triggered are neither filled trades nor a profit recap.

Source: Bitget’s updated official incident statement and the safety announcement on September 25; Kraken public quotes.
#BitgetCEOConfirms$388MStolenInHack #XMR
The above is only my personal market observation and does not constitute investment advice.

Bitget updates BTC withdrawal status｜Two channels open does not mean full recovery｜Around $830,000 I’ll wait

My stance is cautious: withdrawal recovery needs to be precise at the network level, not just chasing longs based on coin name. In Binance Square #BitgetCEOConfirms$388MStolenInHack, this round still has 11 people discussing—same as the previous round; BTC is also on the six-hour search leaderboard. The snapshot does not prove that activity is accelerating further, nor is it evidence of新增新增买盘.

I cross-check Bitget’s official event update: at 08:00 UTC on September 28, BTC withdrawals start resuming as scheduled. The Bitcoin and BSC networks are already open. This is different from the September 26 announcement that only listed the recovery schedule. At this point, we can say “some channels have already been opened”—we shouldn’t keep writing it as an unexecuted plan, and we also can’t expand it into a claim that all BTC withdrawal routes have resumed.

For this round, I use the platform’s publicly available coin interface for cross-verification. Querying BTC shows success: the withdrawable field for the BTC network and BEP20 network is true, while LIGHTNING is false. This is the public status at query time—not me personally completing a withdrawal, and it does not guarantee that any particular account, amount, or address will definitely pass review. If one route isn’t enabled, it doesn’t mean the entire Bitcoin network has stopped operating; future status may also change. Please re-check again before operating.

How does this affect the crypto market? My view is that cross-platform dispatch requires a fully available path. Even if the start point allows withdrawals, you also need to confirm whether the destination accepts the same network, whether the receiving method matches, and the tradable balance after funds arrive. Seeing “BTC recovery” and casually switching networks could turn a trading opportunity into an operational risk. The receiving side’s supported range isn’t confirmed, so I won’t send funds first; the page status cannot replace confirmation that funds have arrived.

Does recovery reduce friction? It can reduce scheduling friction for some routes, but it doesn’t mean overall market liquidity is fully back to pre-event levels, and it doesn’t mean the investigation has ended. I have no data proving how many BTC buyers were added as a result. Transfers between addresses can’t be directly treated as net buying. Channel availability is a prerequisite for trading; order execution depends on price conditions—both need to be verified.

How has the market behaved so far? I re-check Kraken’s USDT spot BTC around $83,032.9. Over the past 24 hours it ranged from $82,566.4 to $85,142.8. It has temporarily returned near $83,000, but it’s still on the lower side of the range. This snapshot cannot prove that the recovery announcement drove the rebound; a single quote crossing the integer level isn’t a confirmation by hourly close. $83,300 is my participation threshold, and $82,200 is the cancellation line before entry—neither guarantees effective support or resistance.

If I were trading myself: I’m not participating right now; position is zero; no shorting, no leverage. Only if the hourly line closes back above $83,300, then retests $83,150 to $83,300 and holds—and if the receiving network, quotes, and deposit/withdrawal paths I actually use are normal—I would use at most 0.3% of total funds to try a spot long. After the $83,800 halving, I would close the remaining position at $84,300. If after entry price hits $82,800 with a hard stop loss, or if two consecutive hourly candles close below $83,150, I’ll close everything remaining. If it breaks below $82,200 before entry, the plan is canceled and I won’t average down losses. If channels become restricted again, the receiving side doesn’t match, or the risk assessment changes due to later investigation, I’ll withdraw participation even if the price meets the conditions. This is not a record of fills or profits.

Source: Bitget official event statement, September 26 recovery announcement, and public coin interface; Kraken market data.
#BitgetCEOConfirms$388MStolenInHack #BTC
The above is only personal market observation and does not constitute investment advice.

Most exchange hacks actually make the market stronger long term

Panic cleans out the weak leverage instantly

Smart money just watches the fear fade and resets risk

Traders need to keep sizing smaller until order books heal

I am sitting on my hands and changing zero right now

Proof I am wrong is if liquidity fails to return across top venues next week

Agree or disagree

#BitgetCEOConfirms$388MStolenInHack #CryptoNews

Withdrawal recovery depends on the channel｜Bitget updates its event statement｜Let’s first observe XMR and confirm 534

My stance is to first verify whether funds can be withdrawn in accordance with the rules, and only then discuss bottom-picking. On Binance Square, there’s currently a #BitgetCEOConfirms$388MStolenInHack hot-topic, but the trending tag isn’t an audit conclusion. In its update, Bitget lists the currently estimated affected amount from the same security incident on September 24 as about $388 million, and also states it may be adjusted as tracking and verification continue; it should not be written as if today has added another incident of the same-sized theft. The original announcement’s estimate was about $351.6 million, which differs from the updated statement—so the timelines need to be distinguished.

This time, I’m more focused on the difference between “account balances unchanged” and “assets that can be withdrawn immediately.” Officially, they say balances are not affected, and trading and deposits continue to operate, while withdrawals are being restored in phases. These claims can coexist: the figures on the books address account record issues, while the withdrawal gateway, supported networks, and settlement status address usability. They don’t automatically prove each other, and they certainly don’t mean I have independently verified the platform’s entire assets. Pausing withdrawals also can’t be directly inferred as insolvency; the official explanation is that it’s a security check measure, and we should still wait for later verifiable information.

Why does this matter to the crypto market? Many traders treat an exchange’s balances as instant cash for cross-platform position rebalancing. Once the exit is temporarily restricted, planned arbitrage, hedging, and margin top-ups may not be executable. The risk isn’t just reflected in a single coin’s price drop—it’s also reflected in the inability to transfer positions in time. In terms of discipline, I won’t move more money into a channel whose recovery hasn’t been confirmed just for easier rebalancing, and I won’t accept any priority-unlock services offered via private messages.

The market reaction should be viewed separately: the Square has already listed this as a hot topic, which shows the community is paying attention. But without reliable evidence of fund flows, you can’t say XMR is absorbing safe-haven buy pressure. At 00:00 Beijing time on September 29, the Kraken XMR/USD quote is about 532.14. Over the past 24 hours, the range was 525.00 to 552.99. The price is near the lower end of the range, not a breakout pattern. This is only a price observation from a single trading venue; it can’t be used to prove that the event caused a drawdown. The official list of affected assets doesn’t include XMR, and you can’t infer from that that all custody platforms holding XMR are safe, nor can you use it to imply that Bitget supports XMR withdrawals.

If I were trading myself: I wouldn’t participate; my position is zero. My direction would only consider a small spot long position once conditions are met, without leverage. Wait until XMR’s hour closing is above 534; then if it retests from 532 to 534 without breaking, consider entering with 3% of total funds. At 540, cut in half; at 546, close the remaining position. After entry, if it falls to 529, execute a stop-loss. If two consecutive hour closes fall below 532, I will close everything—no waiting for a rebound. If, before entry, the price breaks below 524, I’ll cancel this plan. If the quote clearly deviates from the above range, reassess rather than mechanically chasing orders. Until triggered, it’s only a plan—not an executed trade—and there’s nothing to review for profits.

I’ll use the actual withdrawal status on the official platform to verify recovery progress; the “subsequent recovery time” mentioned in the announcement is only scheduling information and can’t be treated as already reopened. If the price loses the lower end of the range again, or if there are new changes to the withdrawal schedule, it will overturn the current small-position observation framework. First ensure the exit path, then weigh potential returns.

#BitgetCEOConfirms$388MStolenInHack $XMR
The above is only my personal market observation and does not constitute investment advice.