Bitget timeline still trending on the square’s hot list | Using a recovery platform doesn’t mean confirming the attacker | ETH around $2,664 — I’ll wait
My attitude is to first separate facts and evidence. Don’t label an attacker based on the recovery platform name, and don’t go long or short ETH because of that. Binance Square #BitgetDetailsSecurityIncidentTimeline has 45 people discussing; when switching tags on the homepage, you can’t compare discussion counts across tabs as “heat” can be accelerated.
The first-hand facts come from Bitget’s official event statement updated on the platform: the platform uses Bybit’s LazarusBounty as one of the asset-recovery channels, and it explicitly states that an independent evidence-gathering investigation is still underway. Findings that have not been formally verified should not be treated as definitive conclusions. During the investigation period, it does not speculate or attribute the attack to any party. Detailed findings will be disclosed through an official security report. The tool name and the incident attribution are two different categories of information, and you can’t write “already confirmed that some organization is responsible” based on the name alone.
I cross-checked Bybit’s official help center. It explains LazarusBounty as a rewards program designed to help identify and freeze illegal funds, and it explicitly distinguishes it from a Bug Bounty that targets vulnerabilities in reporting platforms. This explanation was updated in 2025—not a newly released investigation result today. It helps understand the tool’s purpose, but it cannot replace the forensic evidence for this incident. I also checked Bitget’s September 25 security update; its investigation and fund tracing are still ongoing.
Why does this matter to trading? Wrong attribution may expand a platform-custody incident into threats facing all chains. But since we don’t know who the attacker is, we also can’t ignore the confirmed risks related to certain funds and channels. I’ll first verify the asset location, required permissions, and exit paths, then decide whether to add risk—no need to guess a name first.
Take ETH separately. The official impacted assets include ETH, which does not mean the Ethereum consensus has been breached. Even using recovery channels, there’s no proof that all frozen funds have been returned to users, so it can’t be counted as新增买盘. I’ll wait for the official report and recovery status. I won’t use unverified attribution to endorse a rebound, nor treat tracing work as a liquidity fix.
How has the market responded? I re-check Kraken’s ETH/USD around $2,664.20. Over the past 24 hours it ranged from 2,635.57 to 2,716.32. It has left the low point but hasn’t reached my confirmation threshold, so I can’t attribute it to security-related news. 2,670 is the participation condition; 2,630 is the cancel line before entry. It’s not a guarantee of effective support/resistance. Only if the official report changes the risk assessment or there’s an abnormality in the channels—then if the price condition is met, it can participate.
If I were trading this myself, I wouldn’t participate. Position size is zero—no shorting, no leverage. Only if the hourly candles close above $2,670, and on the retest from $2,665 to $2,670 it holds, and the quoted price and the actual deposit/withdrawal channels are functioning normally, then I would use at most 0.3% of total funds to try a spot long. At $2,690, I’d cut the position in half; at $2,710, I’d close the remaining position. If after entry the price hits a hard stop-loss at $2,648, or if two consecutive hourly candles close below $2,665, I would close everything remaining. If it breaks below $2,630 before entry, I cancel the plan and don’t average down. Plans that haven’t been triggered are not “filled,” and can’t be written as profit.
Sources: Bitget official event statement and the September 25 security update; Bybit official LazarusBounty Q&A; Kraken market data.
#BitgetDetailsSecurityIncidentTimeline #ETH
The above is for personal market observation only and does not constitute investment advice.
My attitude is to first separate facts and evidence. Don’t label an attacker based on the recovery platform name, and don’t go long or short ETH because of that. Binance Square #BitgetDetailsSecurityIncidentTimeline has 45 people discussing; when switching tags on the homepage, you can’t compare discussion counts across tabs as “heat” can be accelerated.
The first-hand facts come from Bitget’s official event statement updated on the platform: the platform uses Bybit’s LazarusBounty as one of the asset-recovery channels, and it explicitly states that an independent evidence-gathering investigation is still underway. Findings that have not been formally verified should not be treated as definitive conclusions. During the investigation period, it does not speculate or attribute the attack to any party. Detailed findings will be disclosed through an official security report. The tool name and the incident attribution are two different categories of information, and you can’t write “already confirmed that some organization is responsible” based on the name alone.
I cross-checked Bybit’s official help center. It explains LazarusBounty as a rewards program designed to help identify and freeze illegal funds, and it explicitly distinguishes it from a Bug Bounty that targets vulnerabilities in reporting platforms. This explanation was updated in 2025—not a newly released investigation result today. It helps understand the tool’s purpose, but it cannot replace the forensic evidence for this incident. I also checked Bitget’s September 25 security update; its investigation and fund tracing are still ongoing.
Why does this matter to trading? Wrong attribution may expand a platform-custody incident into threats facing all chains. But since we don’t know who the attacker is, we also can’t ignore the confirmed risks related to certain funds and channels. I’ll first verify the asset location, required permissions, and exit paths, then decide whether to add risk—no need to guess a name first.
Take ETH separately. The official impacted assets include ETH, which does not mean the Ethereum consensus has been breached. Even using recovery channels, there’s no proof that all frozen funds have been returned to users, so it can’t be counted as新增买盘. I’ll wait for the official report and recovery status. I won’t use unverified attribution to endorse a rebound, nor treat tracing work as a liquidity fix.
How has the market responded? I re-check Kraken’s ETH/USD around $2,664.20. Over the past 24 hours it ranged from 2,635.57 to 2,716.32. It has left the low point but hasn’t reached my confirmation threshold, so I can’t attribute it to security-related news. 2,670 is the participation condition; 2,630 is the cancel line before entry. It’s not a guarantee of effective support/resistance. Only if the official report changes the risk assessment or there’s an abnormality in the channels—then if the price condition is met, it can participate.
If I were trading this myself, I wouldn’t participate. Position size is zero—no shorting, no leverage. Only if the hourly candles close above $2,670, and on the retest from $2,665 to $2,670 it holds, and the quoted price and the actual deposit/withdrawal channels are functioning normally, then I would use at most 0.3% of total funds to try a spot long. At $2,690, I’d cut the position in half; at $2,710, I’d close the remaining position. If after entry the price hits a hard stop-loss at $2,648, or if two consecutive hourly candles close below $2,665, I would close everything remaining. If it breaks below $2,630 before entry, I cancel the plan and don’t average down. Plans that haven’t been triggered are not “filled,” and can’t be written as profit.
Sources: Bitget official event statement and the September 25 security update; Bybit official LazarusBounty Q&A; Kraken market data.
#BitgetDetailsSecurityIncidentTimeline #ETH
The above is for personal market observation only and does not constitute investment advice.
